Layering of post-capture processing in a messaging system

ABSTRACT

Systems and methods described herein provide for retrieving, from a storage device, first image data previously captured by a client device. The systems and methods further detect a selection of a first image processing operation and perform the first image processing operation on the first image data to generate second image data. The systems and methods further detect a selection of a second image processing operation and perform the second image processing operation on the second image data to generate third image data. The systems and methods generate a message comprising the third image data.

CLAIM OF PRIORITY

This application is a continuation of U.S. patent application Ser. No.16/732,051, filed Dec. 31, 2019, which is incorporated herein byreference in its entirety.

BACKGROUND

With the increased use of digital images, affordability of portablecomputing devices, availability of increased capacity of digital storagemedia, and increased bandwidth and accessibility of network connections,digital images have become a part of the daily life for an increasingnumber of people. Users with a range of interests from various locationscan capture digital images of various subjects and make captured imagesavailable to others via networks, such as the Internet. To enhanceusers' experiences with digital images and provide various features,enabling computing devices to perform image processing operations onvarious objects and/or features captured in a wide range of changingconditions (e.g., changes in image scales, noises, lighting, movement,or geometric distortion) can be challenging and computationallyintensive.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 is a diagrammatic representation of a networked environment inwhich the present disclosure may be deployed, in accordance with someexample embodiments.

FIG. 2 is a diagrammatic representation of a messaging clientapplication, in accordance with some example embodiments.

FIG. 3 is a diagrammatic representation of a data structure asmaintained in a database, in accordance with some example embodiments.

FIG. 4 is a diagrammatic representation of a message, in accordance withsome example embodiments.

FIG. 5 is a flowchart for an access-limiting process, in accordance withsome example embodiments.

FIG. 6 is a block diagram illustrating various modules of an annotationsystem that implements a post-processing graphics pipeline, according tocertain example embodiments.

FIG. 7 is a schematic diagram illustrating a structure of the messageannotations, as described in FIG. 4, including additional informationcorresponding to metadata for post-processing an image (e.g., the inputframe), according to some embodiments.

FIG. 8A and FIG. 8B illustrate examples of a user capturing an image forpost-processing in the messaging client application (or the messagingsystem), according to some embodiments.

FIG. 9A and FIG. 9B illustrate examples of post-processing in themessaging client application (or the messaging system), according tosome embodiments.

FIG. 10A and FIG. 10B illustrate other examples of post-processing inthe messaging client application (or the messaging system), according tosome embodiments.

FIG. 11 illustrates examples of user interfaces for selecting a mediaoverlay that applies post-processing to content (e.g., an image orvideo) in the messaging client application (or the messaging system),according to some embodiments.

FIG. 12 illustrates examples of user interfaces for selecting a mediaoverlay that applies post-processing to content (e.g., an image orvideo) in the messaging client application (or the messaging system),according to some embodiments, which follows the examples described inFIG. 11A and FIG. 11B.

FIG. 13 is a schematic diagram of an example of a graphical processingpipeline, namely a post-processing pipeline implemented for components(e.g., a GPU) of the client device, according to some exampleembodiments.

FIG. 14 is a schematic diagram of an example of a graphical processingpipeline, namely a post-processing pipeline implemented for components(e.g., a GPU) of the client device, according to some exampleembodiments.

FIG. 15 is a schematic diagram of an example of a stacking of mediaoverlay layers as implemented via a graphical processing pipeline,namely the post-processing pipeline(s) described above in FIG. 13 and/orFIG. 14, according to some example embodiments.

FIG. 16 illustrates examples of user interfaces (e.g., carousel) forselecting and stacking multiple media overlays for applyingpost-processing to media content (e.g., an image or video) in themessaging client application (or the messaging system), according tosome embodiments.

FIG. 17 illustrates additional examples of user interfaces (e.g.,carousel) for selecting and stacking multiple media overlays forapplying post-processing to media content (e.g., an image or video) inthe messaging client application (or the messaging system), according tosome embodiments.

FIG. 18 illustrates examples of media overlays that can be selected toapply on media content during post-processing.

FIG. 19 illustrates examples of media overlays that can be selected toapply on media content during post-processing.

FIG. 20 illustrates examples of media overlays that can be selected toapply on media content during post-processing.

FIG. 21 illustrates examples of media overlays that can be selected toapply on media content during post-processing.

FIG. 22 illustrates examples of media overlays that can be selected toapply on media content during post-processing.

FIG. 23 illustrates examples of media overlays that can be selected toapply on media content during post-processing.

FIG. 24 illustrates examples of media overlays that can be selected toapply on media content during post-processing.

FIG. 25 illustrates examples of media overlays that can be selected toapply on media content during post-processing.

FIG. 26 is a flowchart illustrating a method to generate a message basedon at least one post-processing operation on image data, according tocertain example embodiments.

FIG. 27 is a flowchart illustrating a method to generate a message basedon layering of post-processing operations on image data, according tocertain example embodiments.

FIG. 28 is a flowchart illustrating a method to provide a carouselinterface for post-processing operations, according to certain exampleembodiments.

FIG. 29 is a flowchart illustrating a method to determine a set of mediaoverlays for populating a set of media overlays that can be utilized bya client electronic device during a post-processing stage to modifymedia content, according to certain example embodiments.

FIG. 30 is block diagram showing a software architecture within whichthe present disclosure may be implemented, in accordance with someexample embodiments.

FIG. 31 is a diagrammatic representation of a machine, in the form of acomputer system within which a set of instructions may be executed forcausing the machine to perform any one or more of the methodologiesdiscussed, in accordance with some example embodiments.

DETAILED DESCRIPTION

As mentioned above, with the increased use of digital images,affordability of portable computing devices, availability of increasedcapacity of digital storage media, and increased bandwidth andaccessibility of network connections, digital images have become a partof the daily life for an increasing number of people. Users with a rangeof interests from various locations can capture digital images ofvarious subjects and make captured images available to others vianetworks, such as the Internet. To enhance users' experiences withdigital images and provide various features, enabling computing devicesto perform image processing operations on various objects and/orfeatures captured in a wide range of changing conditions (e.g., changesin image scales, noises, lighting, movement, or geometric distortion)can be challenging and computationally intensive. Embodiments describedherein provide for an improved system for image processing during apost-capture stage of image data or media content.

As referred to herein, a post-capture stage refers to a period wheremedia content has been captured by a given device (e.g., using a capturesensor such as a camera) and has been stored in a given storage deviceand/or persistent memory device. Further such media content may haveundergone transcoding and/or compression to transform the media contentinto a suitable format for storage. A user of a messaging clientapplication, as described further herein, can retrieve the stored mediacontent at a later time period for applying a set of post-processingimage operations described further herein, which advantageously utilizesthe novel graphical processing pipelines, systems, methods, techniques,and user interfaces as described in more detail herein.

Messaging systems are frequently utilized and are increasingly leveragedby users of mobile computing devices, in various settings, to providedifferent types of functionality in a convenient manner. As describedherein, the subject messaging system comprises practical applicationsthat provide improvements in rendering media overlays on media content(e.g., images, videos, and the like) by at least performingpost-processing operations on the media content. Such post-processingoperations are enabled by at least an extensible graphical renderingpipeline software architecture (as described further herein) whichsupports layering of post-processing operations to provide compositemedia content. Via such an extensible architecture, processing andcomputing improvements can be achieved over existing graphical renderingpipelines. The extensible architecture can further reduce latency inrendering of the post-processing operations compared with imageprocessing operations that are performed in conjunction with imageand/or video capture operations (e.g., via a camera of a givenelectronic computing device).

As referred to herein, the phrase “media overlay” or “media overlays”includes various image processing operations corresponding to an imagemodification, filter, LENSES, and the like, as described further herein.

FIG. 1 is a block diagram showing an example of a messaging system 100for exchanging data (e.g., messages and associated content) over anetwork. The messaging system 100 includes multiple instances of aclient device 102, each of which hosts a number of applicationsincluding a messaging client application 104. Each messaging clientapplication 104 is communicatively coupled to other instances of themessaging client application 104 and a messaging server system 108 via anetwork 106 (e.g., the Internet).

A messaging client application 104 is able to communicate and exchangedata with another messaging client application 104 and with themessaging server system 108 via the network 106. The data exchangedbetween messaging client application 104, and between a messaging clientapplication 104 and the messaging server system 108, includes functions(e.g., commands to invoke functions) as well as payload data (e.g.,text, audio, video or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, the location of certain functionalityeither within the messaging client application 104 or the messagingserver system 108 is a design choice. For example, it may be technicallypreferable to initially deploy certain technology and functionalitywithin the messaging server system 108, but to later migrate thistechnology and functionality to the messaging client application 104where a client device 102 has a sufficient processing capacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Thisdata may include, message content, client device information,geolocation information, media annotation and overlays, message contentpersistence conditions, social network information, and live eventinformation, as examples. Data exchanges within the messaging system 100are invoked and controlled through functions available via userinterfaces (UIs) of the messaging client application 104.

Turning now specifically to the messaging server system 108, anApplication Program Interface (API) server 110 is coupled to, andprovides a programmatic interface to, an application server 112. Theapplication server 112 is communicatively coupled to a database server118, which facilitates access to a database 120 in which is stored dataassociated with messages processed by the application server 112.

The Application Program Interface (API) server 110 receives andtransmits message data (e.g., commands and message payloads) between theclient device 102 and the application server 112. Specifically, theApplication Program Interface (API) server 110 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the messaging client application 104 in order to invoke functionalityof the application server 112. The Application Program Interface (API)server 110 exposes various functions supported by the application server112, including account registration, login functionality, the sending ofmessages, via the application server 112, from a particular messagingclient application 104 to another messaging client application 104, thesending of media files (e.g., images or video) from a messaging clientapplication 104 to the messaging server application 114, and forpossible access by another messaging client application 104, the settingof a collection of media data (e.g., story), the retrieval of a list offriends of a user of a client device 102, the retrieval of suchcollections, the retrieval of messages and content, the adding anddeletion of friends to a social graph, the location of friends within asocial graph, and opening an application event (e.g., relating to themessaging client application 104).

The application server 112 hosts a number of applications andsubsystems, including a messaging server application 114, an imageprocessing system 116, and a social network system 122. The messagingserver application 114 implements a number of message processingtechnologies and functions, particularly related to the aggregation andother processing of content (e.g., textual and multimedia content)included in messages received from multiple instances of the messagingclient application 104. As will be described in further detail, the textand media content from multiple sources may be aggregated intocollections of content (e.g., called stories or galleries). Thesecollections are then made available, by the messaging server application114, to the messaging client application 104. Other processor and memoryintensive processing of data may also be performed server-side by themessaging server application 114, in view of the hardware requirementsfor such processing.

The application server 112 also includes an image processing system 116that is dedicated to performing various image processing operations,typically with respect to images or video received within the payload ofa message at the messaging server application 114.

The social network system 122 supports various social networkingfunctions services, and makes these functions and services available tothe messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph 304 (as shown in FIG.3) within the database 120. Examples of functions and services supportedby the social network system 122 include the identification of otherusers of the messaging system 100 with which a particular user hasrelationships or is “following”, and also the identification of otherentities and interests of a particular user.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120 in which isstored data associated with messages processed by the messaging serverapplication 114.

FIG. 2 is block diagram illustrating further details regarding themessaging system 100, according to example embodiments. Specifically,the messaging system 100 is shown to comprise the messaging clientapplication 104 and the application server 112, which in turn embody anumber of some subsystems, namely an ephemeral timer system 202, acollection management system 204 and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message, orcollection of messages (e.g., a story), selectively display and enableaccess to messages and associated content via the messaging clientapplication 104. Further details regarding the operation of theephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image video and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text and audio) may be organized into an “eventgallery” or an “event story.” Such a collection may be made availablefor a specified time period, such as the duration of an event to whichthe content relates. For example, content relating to a music concertmay be made available as a “story” for the duration of that musicconcert. The collection management system 204 may also be responsiblefor publishing an icon that provides notification of the existence of aparticular collection to the user interface of the messaging clientapplication 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation may be paid to a user for inclusion ofuser-generated content into a collection. In such cases, the curationinterface 208 operates to automatically make payments to such users forthe use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the messaging system 100. The annotation system 206operatively supplies a media overlay or supplementation (e.g., an imagefilter) to the messaging client application 104 based on a geolocationof the client device 102. In another example, the annotation system 206operatively supplies a media overlay to the messaging client application104 based on other information, such as social network information ofthe user of the client device 102. A media overlay may include audio andvisual content and visual effects.

Examples of audio and visual content include pictures, texts, logos,animations, and sound effects. An example of a visual effect includescolor overlaying. The audio and visual content or the visual effects canbe applied to a media content item (e.g., a photo) at the client device102. For example, the media overlay may include text that can beoverlaid on top of a photograph taken by the client device 102. Inanother example, the media overlay includes an identification of alocation overlay (e.g., Venice beach), a name of a live event, or a nameof a merchant overlay (e.g., Beach Coffee House). In another example,the annotation system 206 uses the geolocation of the client device 102to identify a media overlay that includes the name of a merchant at thegeolocation of the client device 102. The media overlay may includeother indicia associated with the merchant. The media overlays may bestored in the database 120 and accessed through the database server 118.

In one example embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map, and upload content associated with the selectedgeolocation. The user may also specify circumstances under which aparticular media overlay should be offered to other users. Theannotation system 206 generates a media overlay that includes theuploaded content and associates the uploaded content with the selectedgeolocation.

In another example embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 206 associates the mediaoverlay of a highest bidding merchant with a corresponding geolocationfor a predefined amount of time.

FIG. 3 is a schematic diagram illustrating data structures 300 which maybe stored in the database 120 of the messaging server system 108,according to certain example embodiments. While the content of thedatabase 120 is shown to comprise a number of tables, it will beappreciated that the data could be stored in other types of datastructures (e.g., as an object-oriented database).

The database 120 includes message data stored within a message table314. The entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events, etc. Regardless of type, any entity regarding which themessaging server system 108 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 304 furthermore stores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization) interested-based or activity-based, merely for example.

The database 120 also stores annotation data, in the example form offilters, in an annotation table 312. Filters for which data is storedwithin the annotation table 312 are associated with and applied tovideos (for which data is stored in a video table 310) and/or images(for which data is stored in an image table 308). Filters, in oneexample, are overlays that are displayed as overlaid on an image orvideo during presentation to a recipient user. Filters may be of variestypes, including user-selected filters from a gallery of filterspresented to a sending user by the messaging client application 104 whenthe sending user is composing a message. Other types of filters includegeolocation filters (also known as geo-filters) which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client application 104, basedon geolocation information determined by a GPS unit of the client device102. Another type of filer is a data filer, which may be selectivelypresented to a sending user by the messaging client application 104,based on other inputs or information gathered by the client device 102during the message creation process. Example of data filters includecurrent temperature at a specific location, a current speed at which asending user is traveling, battery life for a client device 102, or thecurrent time.

Other annotation data that may be stored within the image table 308 isdata corresponding to a lens (e.g., LENSES). As referred to herein, alens is a type of media overlay. One example of a lens is a real-timespecial effect and sound that may be added to an image or video

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe entity table 302. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a story or a gallery). The creation of a particularcollection may be initiated by a particular user (e.g., each user forwhich a record is maintained in the entity table 302). A user may createa “personal story” in the form of a collection of content that has beencreated and sent/broadcast by that user. To this end, the user interfaceof the messaging client application 104 may include an icon that isuser-selectable to enable a sending user to add specific content to hisor her personal story.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automatically,or using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom varies locations and events. Users whose client devices havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client application 104, to contributecontent to a particular live story. The live story may be identified tothe user by the messaging client application 104, based on his or herlocation. The end result is a “live story” told from a communityperspective.

A further type of content collection is known as a “location story”,which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some embodiments, generated by a messaging clientapplication 104 for communication to a further messaging clientapplication 104 or the messaging server application 114. The content ofa particular message 400 is used to populate the message table 314stored within the database 120, accessible by the messaging serverapplication 114. Similarly, the content of a message 400 is stored inmemory as “in-transit” or “in-flight” data of the client device 102 orthe application server 112. The message 400 is shown to include thefollowing components:

-   -   A message identifier 402: a unique identifier that identifies        the message 400.    -   A message text payload 404: text, to be generated by a user via        a user interface of the client device 102 and that is included        in the message 400.    -   A message image payload 406: image data, captured by a camera        component of a client device 102 or retrieved from a memory        component of a client device 102, and that is included in the        message 400.    -   A message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 102 and that is included in the message 400.    -   A message audio payload 410: audio data, captured by a        microphone or retrieved from a memory component of the client        device 102, and that is included in the message 400.    -   A message annotations 412: annotation data (e.g., filters,        stickers or other enhancements) that represents annotations to        be applied to message image payload 406, message video payload        408, or message audio payload 410 of the message 400.    -   A message duration parameter 414: parameter value indicating, in        seconds, the amount of time for which content of the message        (e.g., the message image payload 406, message video payload 408,        message audio payload 410) is to be presented or made accessible        to a user via the messaging client application 104.    -   A message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message. Multiple message geolocation        parameter 416 values may be included in the payload, each of        these parameter values being associated with respect to content        items included in the content (e.g., a specific image into        within the message image payload 406, or a specific video in the        message video payload 408).    -   A message story identifier 418: identifier values identifying        one or more content collections (e.g., “stories”) with which a        particular content item in the message image payload 406 of the        message 400 is associated. For example, multiple images within        the message image payload 406 may each be associated with        multiple content collections using identifier values.    -   A message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   A message sender identifier 422: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 on        which the message 400 was generated and from which the message        400 was sent    -   A message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 to        which the message 400 is addressed.

The contents (e.g., values) of the various components of message 400 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 406 maybe a pointer to (or address of) a location within an image table 308.Similarly, values within the message video payload 408 may point to datastored within a video table 310, values stored within the messageannotations 412 may point to data stored in an annotation table 312,values stored within the message story identifier 418 may point to datastored in a story table 306, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message group 504) may be time-limited (e.g., madeephemeral).

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the messaging client application 104. Inone embodiment, an ephemeral message 502 is viewable by a receiving userfor up to a maximum of 10 seconds, depending on the amount of time thatthe sending user specifies using the message duration parameter 506.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized implementation of theephemeral timer system 202, which is responsible for the overall timingof display of content (e.g., an ephemeral message 502) to a receivinguser.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message group 504 (e.g., a collection of messages in apersonal story, or an event story). The ephemeral message group 504 hasan associated group duration parameter 508, a value of which determinesa time-duration for which the ephemeral message group 504 is presentedand accessible to users of the messaging system 100. The group durationparameter 508, for example, may be the duration of a music concert,where the ephemeral message group 504 is a collection of contentpertaining to that concert. Alternatively, a user (either the owninguser or a curator user) may specify the value for the group durationparameter 508 when performing the setup and creation of the ephemeralmessage group 504.

Additionally, each ephemeral message 502 within the ephemeral messagegroup 504 has an associated group participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message group504. Accordingly, a particular ephemeral message group 504 may “expire”and become inaccessible within the context of the ephemeral messagegroup 504, prior to the ephemeral message group 504 itself expiring interms of the group duration parameter 508. The group duration parameter508, group participation parameter 510, and message receiver identifier424 each provide input to a group timer 514, which operationallydetermines, firstly, whether a particular ephemeral message 502 of theephemeral message group 504 will be displayed to a particular receivinguser and, if so, for how long. Note that the ephemeral message group 504is also aware of the identity of the particular receiving user as aresult of the message receiver identifier 424.

Accordingly, the group timer 514 operationally controls the overalllifespan of an associated ephemeral message group 504, as well as anindividual ephemeral message 502 included in the ephemeral message group504. In one embodiment, each and every ephemeral message 502 within theephemeral message group 504 remains viewable and accessible for atime-period specified by the group duration parameter 508. In a furtherembodiment, a certain ephemeral message 502 may expire, within thecontext of ephemeral message group 504, based on a group participationparameter 510. Note that a message duration parameter 506 may stilldetermine the duration of time for which a particular ephemeral message502 is displayed to a receiving user, even within the context of theephemeral message group 504. Accordingly, the message duration parameter506 determines the duration of time that a particular ephemeral message502 is displayed to a receiving user, regardless of whether thereceiving user is viewing that ephemeral message 502 inside or outsidethe context of an ephemeral message group 504.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message group 504based on a determination that it has exceeded an associated groupparticipation parameter 510. For example, when a sending user hasestablished a group participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message group 504 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message group 504 either when the groupparticipation parameter 510 for each and every ephemeral message 502within the ephemeral message group 504 has expired, or when theephemeral message group 504 itself has expired in terms of the groupduration parameter 508.

In certain use cases, a creator of a particular ephemeral message group504 may specify an indefinite group duration parameter 508. In thiscase, the expiration of the group participation parameter 510 for thelast remaining ephemeral message 502 within the ephemeral message group504 will determine when the ephemeral message group 504 itself expires.In this case, a new ephemeral message 502, added to the ephemeralmessage group 504, with a new group participation parameter 510,effectively extends the life of an ephemeral message group 504 to equalthe value of the group participation parameter 510.

Responsive to the ephemeral timer system 202 determining that anephemeral message group 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (and, for example, specifically the messaging client application104) to cause an indicium (e.g., an icon) associated with the relevantephemeral message group 504 to no longer be displayed within a userinterface of the messaging client application 104. Similarly, when theephemeral timer system 202 determines that the message durationparameter 506 for a particular ephemeral message 502 has expired, theephemeral timer system 202 causes the messaging client application 104to no longer display an indicium (e.g., an icon or textualidentification) associated with the ephemeral message 502.

FIG. 6 is a block diagram 600 illustrating various modules of anannotation system 206 that implements a post-processing graphicspipeline, according to certain example embodiments. The annotationsystem 206 is shown as including a tracking engine 610, apost-processing engine 620, a rendering engine 630, and a sharing engine640. The various modules of the annotation system 206 are configured tocommunicate with each other (e.g., via a bus, shared memory, or aswitch). Any one or more of these modules may be implemented using oneor more computer processors 605 (e.g., by configuring such one or morecomputer processors to perform functions described for that module) andhence may include one or more of the computer processors 605 (e.g., aset of processors provided by the client device 102). In anotherembodiment, the computer processors 605 refers to a set of processorsprovided by a server or server system, such as the messaging serversystem 108.

Any one or more of the modules described may be implemented usinghardware alone (e.g., one or more of the computer processors 605 of amachine (e.g., machine 3100) or a combination of hardware and software.For example, any described module of the annotation system 206 mayphysically include an arrangement of one or more of the computerprocessors 605 (e.g., a subset of or among the one or more computerprocessors of the machine (e.g., machine 3100) configured to perform theoperations described herein for that module. As another example, anymodule of the annotation system 206 may include software, hardware, orboth, that configure an arrangement of one or more computer processors605 (e.g., among the one or more computer processors of the machine(e.g., machine 3100) to perform the operations described herein for thatmodule. Accordingly, different modules of the annotation system 206 mayinclude and configure different arrangements of such computer processors605 or a single arrangement of such computer processors 605 at differentpoints in time. Moreover, any two or more modules of the annotationsystem 206 may be combined into a single module, and the functionsdescribed herein for a single module may be subdivided among multiplemodules. Furthermore, according to various example embodiments, modulesdescribed herein as being implemented within a single machine, database,or device may be distributed across multiple machines, databases, ordevices.

For the purpose of clarity in explaining the technical concepts below,the following discussion relates to a single input frame. However, it isunderstood that for media content including multiple frames (e.g., avideo), the following discussion would also be applicable.

The post-processing engine 620 receives an input frame 602 captured by aclient device 102 such as included in a captured image or video. Forexample, the input frame 602 can be an image captured by an opticalsensor (e.g., camera) of the client device 102 during capture of animage or video. An image, in an example, includes one or more real-worldfeatures, such a physical object(s) detected in the image. In someembodiments, the input frame 602 includes metadata describing the imageand/or other information as discussed further herein.

As further illustrated, the tracking engine 610 receives the input frame602 (or alternatively a duplicate of the input frame 602 in anembodiment). The tracking engine 610 can include various trackingfunctionality based on a type of object to track. In an example, thetracking engine 610 includes tracking capabilities for surface tracking,face tracking, object tracking, and the like. In an implementation, thetracking engine 610 may only execute one of each of a plurality oftracking processes at a time for facilitating the management ofcomputing resources at the client device 102. In addition, the trackingengine 610 may perform one or more object recognition operations on theinput frame 602.

As referred to herein, tracking refers to operations for determiningspatial properties (e.g., position and/or orientation) of a given object(or portion thereof) during the post-processing stage. In animplementation, during tracking, the object's position and orientationare measured in a continuous manner. Different objects may be tracked,such as a user's head, eyes, or limbs, surfaces, or other objects.Tracking involves dynamic sensing and measuring to enable virtualobjects and/or effects to be rendered with respect to physical objectsin a three-dimensional space corresponding to a scene (e.g., the inputframe 602). Thus, the tracking engine 610 determines metricscorresponding to at least the relative position and orientation of oneor more physical objects in the input frame 602 and includes thesemetrics in tracking data 606 which is provided to the post-processingengine 620. In an example, the tracking engine 610 updates (e.g., trackover time) such metrics from frame to subsequent frame.

In an implementation, the annotation system 206 can utilize techniqueswhich combines information from the device's motion sensors (e.g.,accelerometer and gyroscope sensors, and the like) with an analysis ofthe scene provided in the input frame 602. For example, the annotationsystem 206 detects features in the input frame 602, and as a result,tracks differences in respective positions of such features acrossseveral input frames using information derived at least in part on datafrom the motion sensors of the device.

As mentioned herein, surface tracking refers to operations for trackingone or more representations of surfaces corresponding to planes (e.g., agiven horizontal plane, a floor, a table) in the input frame. In anexample, surface tracking is accomplished using hit testing and/or raycasting techniques. Hit testing, in an example, determines whether aselected point (e.g., pixel or set of pixels) in the input frameintersects with a surface or plane of a representation of a physicalobject in the input frame. Ray casting, in an example, utilizes aCartesian based coordinate system (e.g., x and y coordinates) andprojects a ray (e.g., vector) into the camera's view of the world, ascaptured in the input frame, to detect planes that the ray intersects.

As mentioned herein, face tracking refers to operations for trackingrepresentations of facial features, such as portions of a user's face,in the input frame. In some embodiments, the tracking engine 610includes facial tracking logic to identify all or a portion of a facewithin the one or more images and track landmarks of the face across theset of images of the video stream. As mentioned herein, object trackingrefers to tracking a representation of a physical object in the inputframe.

In an implementation, the tracking engine 610 provides, as output,tracking data 606 corresponding to the aforementioned metrics (e.g.,position and orientation). In some instances, the tracking engine 610includes logic for shape recognition, edge detection, or any othersuitable object detection mechanism. The object of interest may also bedetermined by the tracking engine 610 to be an example of apredetermined object type, matching shapes, edges, or landmarks within arange to an object type of a set of predetermined object types.

The post-processing engine 620 modifies virtual content (e.g., changingits size, scale, direction/orientation, color, shape) such as performingan operation that affects the visual appearance and/or position of avirtual object(s) that may be anchored to a representation of a physicalobject in the scene of the input frame 602.

The post-processing engine 620 receives media overlay metadata 604 andinput frame 602. In an example, media overlay metadata 604 includesinformation regarding a set of media overlays that are applied, by thepost-processing engine 620, as effects to the input frame 602. In anexample, the media overlay metadata 604 includes information describedfurther below in connection with FIG. 7, which may be included as part(or stored separately) from the input frame 602.

The post-processing engine 620, in an embodiment, utilizes machinelearning techniques for applying image processing to facial features inthe input frame 602, using the media overlay metadata 604. One exampleof a machine learning model is a machine learning model (e.g., one ormore neural networks) that has been trained to generate an “averageface” by marking of the borders of facial features based on trainingdata (e.g., several thousands of images). In this example, the machinelearning model generates an “average face” that can be utilized to alignwith a face detected (e.g., object of interest) in the input frame 602for use in performing image processing to modify the input frame togenerate an output frame 608. Additionally, the post-processing engine620 may perform the one or more modifications to the portions of theabove-mentioned object of interest to generate the modified input frame(e.g., the output frame 608).

In one embodiment, the post-processing engine 620, in cooperation withthe sharing engine 640, generates a message. The message includes theoutput frame 608, the media overlay metadata 609 and/or other metadata(e.g., as described herein), and in some instances, the original inputframe 602. The sharing engine 640 transmits the generated message fromthe client device 102 to one or more other client devices, the messagingserver system 108, or a storage device of the client device 102.Further, it is to be understood that by including the original inputframe 602, example embodiments enable providing non-destructive editingfor the message whereby a different image processing operation can beapplied to the original input frame 602, which replaces previous imageprocessing operation performed on output frame 608.

Further, the rendering engine 630 performs rendering of content fordisplay by the messaging client application 104 using the media overlaymetadata 609. The rendering may be performed in conjunction withgraphical processing pipelines and/or media overlay stacking (e.g., theapplication of multiple media overlays to media content) describedfurther herein.

Although the above discussion with respect to FIG. 6 refers to an inputframe, it is appreciated that the aforementioned components of theannotation system can perform similar operations on a set of images(e.g., video) corresponding to respective frames of such video content.

FIG. 7 is a schematic diagram illustrating a structure of the messageannotations 412, as described in FIG. 4, including additionalinformation corresponding to metadata for post-processing an image(e.g., the input frame 702), according to some embodiments.

In an embodiment, the content of a particular message 400, as shown inFIG. 3, including the additional data shown in FIG. 7 is used topopulate the message table 314 stored within the database 120 for agiven message, which is then accessible by the messaging clientapplication 104. As illustrated in FIG. 7, message annotations 412includes the following components corresponding to data in connectionwith post-processing operations:

-   -   media overlay identifier 752: identifier of a media overlay        utilized in the message with post-processing    -   message identifier 754: identifier of the message with        post-processing    -   asset identifiers 756: a set of identifiers for assets in the        message with post-processing. For example, respective asset        identifiers can be included for assets that are determined by        the particular media overlay. In an embodiment, such assets are        created by the media overlay on the sender side client device,        uploaded to the messaging server application 114, and utilized        on the receiver side client device in order to recreate the        message. Examples of typical assets include:        -   The original still RGB image(s) captured by the camera        -   The post-processed image(s) with media overlay effects            applied to the original image    -   media overlay metadata 758: additional metadata associated with        the media overlay corresponding to the media overlay identifier        752, such as:        -   media overlay category: corresponding to a type or            classification for a particular media overlay        -   media overlay carousel index        -   carousel group: This can be populated and utilized when            eligible post-capture media overlays are inserted into a            carousel interface. In an implementation, a new value            “POST_CAPTURE_LENS_DEFAULT_GROUP” (e.g., a default group            assigned to a post capture media overlay can be added to the            list of valid group names, and post-capture media overlays            can be included this group unless another group is already            explicitly set corresponding to metadata for a geolocation            entity in the datastore.    -   capture metadata 760 corresponding to additional metadata, such        as:        -   camera image metadata            -   camera intrinsic data                -   focal length                -   principal point            -   other camera information (e.g., camera position)        -   sensor information            -   gyroscopic sensor data            -   position sensor data            -   accelerometer sensor data            -   other sensor data            -   location sensor data

FIG. 8A and FIG. 8B illustrate examples of a user capturing an image forpost-processing in the messaging client application 104 (or themessaging system 100), according to some embodiments.

FIG. 8A illustrates an example situation in which a user 802 iscapturing an image of a physical item in accordance with variousembodiments. Although only a portable client device (e.g., the clientdevice 102) is shown in FIG. 8A, it should be understood that varioustypes of electronic or computing devices are capable of capturing,receiving and/or processing images in accordance with variousembodiments discussed herein. These client devices can include, forexample desktop PCs, laptop computers, tablet computers, personal dataassistants (PDAs), smart phones, portable media file players, e-bookreaders, portable computers, head-mounted displays, interactive kiosks,mobile phones, net books, single-board computers (SBCs), embeddedcomputer systems, wearable computers (e.g., watches or glasses), gamingconsoles, home-theater PCs (HTPCs), TVs, DVD players, digital cableboxes, digital video recorders (DVRs), computer systems capable ofrunning a web-browser, or a combination of any two or more of these, andthe like.

The client device 102 may have at least one camera 806. Each camera maybe, for example, a charge-coupled device (CCD), an active pixel sensorin complementary metal-oxide-semiconductor (CMOS) or N-typemetal-oxide-semiconductor (NMOS), an infrared or ultrasonic imagesensor, or an image sensor utilizing other type of image capturingtechnologies.

As illustrated in the example of FIG. 8A, the user 802 can position theclient device 102 such that the user's face, including various facialfeatures, are within a field of view 808 of at least one camera 806 ofthe client device 102. The at least one camera 806 can capture a stillimage, which can be stored to local and/or remote storage forpost-processing at a subsequent time. In some embodiments, the at leastone camera 806 captures video, providing a “live” view of the capturedvideo information, which can be stored to local and/or remote storagefor post-processing at a subsequent time.

In a post-capture stage, the previous captured image is accessed fromstorage for further processing (e.g., post-processing). An image 812,including a representation of the face of the user 802, is displayed ona display screen 852 of the client device 102, as illustrated in theexample of FIG. 8B. The user can then select various media overlays forapplying effects and modifications to the displayed image.

FIG. 9A and FIG. 9B illustrate examples of post-processing in themessaging client application 104 (or the messaging system 100),according to some embodiments. As shown in these examples, exampleembodiments enable applying various media overlays to previouslycaptured images and/or videos in different layers such that respectivegraphical elements and/or effects are overlaid upon one another.

As illustrated in FIG. 9A and FIG. 9B, the client device 102 can providefor display of a media overlay, which may include visual and audiocontent corresponding to animations, media content, text content, andthe like. It is appreciated that the media overlay displayed by theclient device 102 can include audio and visual content and visualeffects as described before in respect to FIG. 1 and FIG. 2.

As illustrated in FIG. 9A, an image 812 including the representation ofthe face of the user 802 is shown in the display screen 852 of theclient device 102. A first media overlay 910 is applied to the image812. Embodiments of the subject technology enable multiple mediaoverlays to be applied to a given image, such as the image 812.

As illustrated in FIG. 9B, a second media overlay 912 is applied to theimage comprising the first media overlay. The second media overlay 912is displayed in conjunction with the first media overlay 910 in thedisplay screen 852. In this manner, multiple media overlays can beapplied to the image resulting in effects and graphical elements thatare displayed in conjunction with the image to provide a composite imagewith several applied media overlays.

FIG. 10A and FIG. 10B illustrate other examples of post-processing inthe messaging client application 104 (or the messaging system 100),according to some embodiments. As shown in these additional examples,example embodiments enable various media overlays to be applied topreviously captured images and/or videos in different layers such thatrespective graphical elements and/or effects are overlaid upon oneanother. More specifically, the examples shown in FIGS. 10A and 10Binclude images of multiple users upon which respective media overlayscan be applied as post-processing operations, in varying degrees, inorder to provide visual and/or audio effects which may be provided fordisplay in conjunction with one another.

As illustrated in FIG. 10A and FIG. 10B, the client device 102 providesfor display a media overlay, which may include visual and audio contentcorresponding to animations, media content, text content, and the like.As mentioned before, it is to be appreciated that the media overlaydisplayed by the client device 102 can include audio and visual contentand visual effects as described before with respect to FIG. 1 and FIG.2.

As illustrated in FIG. 10A, an image 1010 includes a representation of ascene including several users (e.g., different persons) shown in thedisplay screen 852 of the client device 102. A first media overlay 1012is applied to a first user in the center of the scene that, asillustrated, provides a graphical representation of virtual glasses(e.g., virtual eyeglasses or spectacles).

As illustrated in FIG. 10B, a second media overlay 1014 and a thirdmedia overlay 1016 are applied to the image 1010 with the first mediaoverlay. The second media overlay 1014 and the third media overlay 1016are displayed in conjunction with the first media overlay 1012. In thisexample, the second media overlay 1014 includes an animation ofgraphical elements (e.g., virtual representations of leaves), and thethird media overlay 1016 includes graphical elements that occluderespective faces of users. As a result, multiple media overlays can beapplied to the image with multiple persons resulting in effects andgraphical elements that are displayed in conjunction with the image toprovide a composite image with several applied media overlays.

To enable the selection of media overlays for applying, as one or morepost-processing operations, example embodiments provide various userinterface implementations to facilitate an interactive user-facingexperience which responds to various inputs provided by a given user. Insome embodiments, the messaging client application 104 can provide theexample user interface as discussed below with respect to FIG. 11.

In the following discussion, example embodiments enable the delivery andorganized presentation of media overlays for post-processing mediacontent. In some examples, media overlays can be displayed inconjunction, during a post-processing stage, with previously capturedmedia content (e.g., images and/or video). As described further herein,when a user performs a particular touch input gesture (e.g., swipe, ordrag gesture) within a user interface, a particular media overlay isidentified and presented to the user.

FIG. 11 illustrates examples of user interfaces for selecting a mediaoverlay that applies post-processing to content (e.g., an image orvideo) in the messaging client application 104 (or the messaging system100), according to some embodiments.

As illustrated in FIG. 11, the client device 102 provides for display ofa media overlay, which may include visual and audio contentcorresponding to animations, media content, text content, and the like.As mentioned before, it is to be appreciated that the media overlaydisplayed by the client device 102 can include audio and visual contentand visual effects as described above with respect to FIG. 1 and FIG. 2.

As illustrated in user interface 1100, an image 1105 corresponding to arepresentation of a scene with a portrait of a person, including a firstmedia overlay 1110 (e.g., graphical text indicating a day of the week),is displayed in the display screen 852 of the client device 102. In anexample, the first media overlay 1110 is selected based on a gestureinput (e.g., swipe, touch input, and the like) which provides arendering of the selected first media overlay 1110 to display a previewof the media overlay on the image. In the examples of FIG. 11, a gestureinput can be received by the messaging client application 10 (or themessaging system 100), which triggers a selection of a respective mediaoverlay which is then provided for display, which may also result in acurrent respective media overlay to be removed from the rendering of thecomposite image including one or more media overlays.

As further shown, in the user interface 1100, a second media overlay1120 is provided for display in the display screen 852 of the clientdevice 102. The second media overlay 1120, in an example, is displayedin response to a gesture input (e.g., swipe) and then displayed in aprogressive manner as the gesture input moves across the display screen852 of the client device 102 (e.g., as indicated by the leftward arrow).The second media overlay 1120 also includes a text and icon overlay 1130indicating a description of the selected media overlay for applyingduring post-processing (e.g., “Biker Bearded Guy”). The second mediaoverlay 1120, in this example, serves as a transition effect totransition between the first media overlay 1110 to the newly selectedmedia overlay. As further shown, the first media overlay 1110 is shownto move outside and eventually disappearing from the display screen 852as the gesture input progresses across the display screen 852.

FIG. 12 illustrates examples of user interfaces for selecting a mediaoverlay that applies post-processing to content (e.g., an image orvideo) in the messaging client application 104 (or the messaging system100), according to some embodiments, which follows the examplesdescribed in FIG. 11A and FIG. 11B.

As illustrated in FIG. 12, the client device 102 can provide for displayof a media overlay, which may include visual and audio contentcorresponding to animations, media content, text content, and the like.As mentioned before, it is appreciated that the media overlay displayedby the client device 102 can include audio and visual content and visualeffects as described before in FIG. 1 and FIG. 2.

As illustrated in user interface 1100, an image corresponding to arepresentation of a scene 1205 with a portrait of a person (e.g., thesame or similar representation to that in FIG. 11 described above),including the second media overlay 1120 (e.g., the transition effect)and the text and icon overlay 1130, is displayed in the display screen852 of the client device 102. In an example, the second media overlay1120 is displayed in the entirety of the display screen 852 after theend of the gesture input (e.g., swipe, touch input, and the like)described above in FIG. 11. As further shown, a graphical indicator 1210is displayed to indicate that post-processing operations in connectionwith the selected media overlay are currently being performed (e.g., asa background process) in preparation for rendering the selected mediaoverlay.

As further shown in the user interface 1100, the selected media overlayis now displayed as a third media overlay 1230 in the representation ofthe scene 1205 with the portrait of the person in the display screen 852of the client device 102. In this manner, different selected mediaoverlay may be provided for display utilizing one or more gestureinputs. In a further example, a subsequent gesture input may be receivedwhich repeats similar operations described in FIG. 11 and FIG. 12 inwhich another media overlay is applied to the representation of thescene.

Although gesture inputs are discussed in the examples of FIG. 11 andFIG. 12, it is appreciated that other inputs can be received includingnon-touch based inputs and/or movement based inputs (e.g., from ahead-mounted display, such as a virtual reality (VR), mixed reality(MR), or augmented reality (AR) device).

As described above, media overlays, such as LENSES, overlays, imagetransformations, AR images and similar terms refer to modifications thatmay be made to videos or images. This includes real-time modificationwhich modifies an image as it is captured using a device sensor and thendisplayed on a screen of the device with the modifications. This alsoincludes modifications to stored content, such as video clips in agallery that may be modified. For example, in a device with access tomultiple media overlays (e.g., LENSES), a user can use a single videoclip with multiple LENSES to see how the different LENSES will modifythe stored clip. For example, multiple LENSES that apply differentpseudorandom movement models can be applied to the same content byselecting different LENSES for the content. Similarly, real-time videocapture may be used with an illustrated modification to show how videoimages currently being captured by sensors of a device would modify thecaptured data. Such data may simply be displayed on the screen and notstored in memory, or the content captured by the device sensors may berecorded and stored in memory with or without the modifications (orboth). In some systems, a preview feature can show how different LENSESwill look within different windows in a display at the same time. Thiscan, for example, enable multiple windows with different pseudorandomanimations to be viewed on a display at the same time.

Data and various systems to use LENSES or other such transform systemsto modify content using this data can thus involve detection of objects(e.g. faces, hands, bodies, cats, dogs, surfaces, objects, etc.),tracking of such objects as they leave, enter, and move around the fieldof view in video frames, and the modification or transformation of suchobjects as they are tracked. In various embodiments, different methodsfor achieving such transformations may be used. For example, someembodiments may involve generating a three-dimensional mesh model of theobject or objects, and using transformations and animated textures ofthe model within the video to achieve the transformation. In otherembodiments, tracking of points on an object may be used to place animage or texture (which may be two dimensional or three dimensional) atthe tracked position. In still further embodiments, neural networkanalysis of video frames may be used to place images, models, ortextures in content (e.g. images or frames of video). Lens data thusrefers both to the images, models, and textures used to createtransformations in content, as well as to additional modeling andanalysis information needed to achieve such transformations with objectdetection, tracking, and placement.

Real time video processing can be performed with any kind of video data,(e.g. video streams, video files, etc.) saved in a memory of acomputerized system of any kind. For example, a user can load videofiles and save them in a memory of a device, or can generate a videostream using sensors of the device. Additionally, any objects can beprocessed using a computer animation model, such as a human's face andparts of a human body, animals, or non-living things such as chairs,cars, or other objects.

In some embodiments, when a particular modification is selected alongwith content to be transformed, elements to be transformed areidentified by the computing device, and then detected and tracked ifthey are present in the frames of the video. The elements of the objectare modified according to the request for modification, thustransforming the frames of the video stream. Transformation of frames ofa video stream can be performed by different methods for different kindsof transformation. For example, for transformations of frames mostlyreferring to changing forms of object's elements characteristic pointsfor each of element of an object are calculated (e.g. using an ActiveShape Model (ASM) or other known methods). Then, a mesh based on thecharacteristic points is generated for each of the at least one elementof the object. This mesh used in the following stage of tracking theelements of the object in the video stream. In the process of tracking,the mentioned mesh for each element is aligned with a position of eachelement. Then, additional points are generated on the mesh. A first setof first points is generated for each element based on a request formodification, and a set of second points is generated for each elementbased on the set of first points and the request for modification. Then,the frames of the video stream can be transformed by modifying theelements of the object on the basis of the sets of first and secondpoints and the mesh. In such method a background of the modified objectcan be changed or distorted as well by tracking and modifying thebackground.

In one or more embodiments, transformations changing some areas of anobject using its elements can be performed by calculating ofcharacteristic points for each element of an object and generating amesh based on the calculated characteristic points. Points are generatedon the mesh, and then various areas based on the points are generated.The elements of the object are then tracked by aligning the area foreach element with a position for each of the at least one element, andproperties of the areas can be modified based on the request formodification, thus transforming the frames of the video stream.Depending on the specific request for modification properties of thementioned areas can be transformed in different ways. Such modificationsmay involve: changing color of areas; removing at least some part ofareas from the frames of the video stream; including one or more newobjects into areas which are based on a request for modification; andmodifying or distorting the elements of an area or object. In variousembodiments, any combination of such modifications or other similarmodifications may be used. For certain models to be animated, somecharacteristic points can be selected as control points to be used indetermining the entire state-space of options for the model animation.

In some embodiments of a computer animation model to transform imagedata using face detection, the face is detected on an image with use ofa specific face detection algorithm (e.g. Viola-Jones). Then, an ActiveShape Model (ASM) algorithm is applied to the face region of an image todetect facial feature reference points.

In other embodiments, other methods and algorithms suitable for facedetection can be used. For example, in some embodiments, features arelocated using a landmark which represents a distinguishable pointpresent in most of the images under consideration. For facial landmarks,for example, the location of the left eye pupil may be used. In aninitial landmark is not identifiable (e.g. if a person has an eyepatch),secondary landmarks may be used. Such landmark identification proceduresmay be used for any such objects. In some embodiments, a set oflandmarks forms a shape. Shapes can be represented as vectors using thecoordinates of the points in the shape. One shape is aligned to anotherwith a similarity transform (allowing translation, scaling, androtation) that minimizes the average Euclidean distance between shapepoints. The mean shape is the mean of the aligned training shapes.

In some embodiments, a search for landmarks from the mean shape alignedto the position and size of the face determined by a global facedetector is started. Such a search then repeats the steps of suggestinga tentative shape by adjusting the locations of shape points by templatematching of the image texture around each point and then conforming thetentative shape to a global shape model until convergence occurs. Insome systems, individual template matches are unreliable and the shapemodel pools the results of the weak template matchers to form a strongeroverall classifier. The entire search is repeated at each level in animage pyramid, from coarse to fine resolution.

Embodiments of a transformation system can capture an image or videostream on a client device and perform complex image manipulationslocally on a client device such as client device 102 while maintaining asuitable user experience, computation time, and power consumption. Thecomplex image manipulations may include size and shape changes, emotiontransfers (e.g., changing a face from a frown to a smile), statetransfers (e.g., aging a subject, reducing apparent age, changinggender), style transfers, graphical element application, and any othersuitable image or video manipulation implemented by a convolutionalneural network that has been configured to execute efficiently on aclient device.

In some example embodiments, a computer animation model to transformimage data can be used by a system where a user may capture an image orvideo stream of the user (e.g., a selfie) using a client device 102having a neural network operating as part of a messaging application 104operating on the client device 102. The transform system operatingwithin the messaging application 104 determines the presence of a facewithin the image or video stream and provides modification iconsassociated with a computer animation model to transform image data, orthe computer animation model can be present as associated with aninterface described herein. The modification icons include changes whichmay be the basis for modifying the user's face within the image or videostream as part of the modification operation. Once a modification iconis selected, the transform system initiates a process to convert theimage of the user to reflect the selected modification icon (e.g.,generate a smiling face on the user). In some embodiments, a modifiedimage or video stream may be presented in a graphical user interfacedisplayed on the mobile client device as soon as the image or videostream is captured and a specified modification is selected. Thetransform system may implement a complex convolutional neural network ona portion of the image or video stream to generate and apply theselected modification. That is, the user may capture the image or videostream and be presented with a modified result in real time or near realtime once a modification icon has been selected. Further, themodification may be persistent while the video stream is being capturedand the selected modification icon remains toggled. Machine taughtneural networks may be used to enable such modifications.

In some embodiments, the graphical user interface, presenting themodification performed by the transform system, may supply the user withadditional interaction options. Such options may be based on theinterface used to initiate the content capture and selection of aparticular computer animation model (e.g. initiation from a contentcreator user interface). In various embodiments, a modification may bepersistent after an initial selection of a modification icon. The usermay toggle the modification on or off by tapping or otherwise selectingthe face being modified by the transformation system. and store it forlater viewing or browse to other areas of the imaging application. Wheremultiple faces are modified by the transformation system, the user maytoggle the modification on or off globally by tapping or selecting asingle face modified and displayed within a graphical user interface. Insome embodiments, individual faces, among a group of multiple faces, maybe individually modified or such modifications may be individuallytoggled by tapping or selecting the individual face or a series ofindividual faces displayed within the graphical user interface.

In some example embodiments, a graphical processing pipelinearchitecture is provided that enables different media overlays to beapplied in corresponding different layers. Such a graphical processingpipeline provides an extensible rendering engine for providing multiplemedia overlays that are included in a composite media (e.g., image orvideo) for rendering by the messaging client application 104 (or themessaging system 100).

In implementations described herein, computer graphics systems, whichcan render two-dimensional (2D) objects or objects from athree-dimensional (3D) world (real or imaginary) onto a 2D displayscreen, are currently used in a wide variety of applications. Such agraphics system (e.g., one included on the client device 102) includes agraphics processing unit (GPU) in some implementations for performingimage processing operations and rendering graphical elements fordisplay. The following discussion below with respect to FIG. 13 and FIG.14 describes example graphical processing pipelines. In some embodimentsthe example graphical processing pipelines are utilized in conjunctionwith the operations described above in respect to at least FIG. 8A, FIG.8B, FIG. 9A, FIG. 9B, FIG. 10A, FIG. 10B, FIG. 11, and FIG. 12, toprovide layering of various media overlays for post-processing of mediacontent.

In an implementation, the GPU includes a logical graphical processingpipeline, which can receive a representation of a 2D or 3D scene andprovide an output of a bitmap that represents a 2D image for display.Existing application programming interfaces (APIs) have implementedgraphical pipeline models. Examples of such APIs include the OpenGraphics Library (OPENGL) API and the METAL API. The graphicalprocessing pipeline includes a number of stages to convert a group ofvertices, textures, buffers, and state information into an image frameon the screen. In an implementation, one of the stages of the graphicalprocessing pipeline is a shader, which may be utilized as part of aparticular media overlay that is applied to an input frame (e.g., imageor video). A shader can be implemented as code running on a specializedprocessing unit, also referred to as a shader unit or shader processor,usually executing several computing threads, programmed to generateappropriate levels of color and/or special effects to fragments beingrendered. For example, a vertex shader processes attributes (position,texture coordinates, color, etc.) of a vertex, and a pixel shaderprocesses attributes (texture values, color, z-depth and alpha value) ofa pixel. In some instances, a pixel shader is referred to as a fragmentshader.

It is to be appreciated that other types of shader processes may beprovided. In an example, a particular sampling rate is utilized, withinthe graphical processing pipeline, for rendering an entire frame, and/orpixel shading is performed at a particular per-pixel rate. In thismanner, a given electronic device (e.g., the client device 102) operatesthe graphical processing pipeline to convert information correspondingto objects into a bitmap that can be displayed by the electronic device.In some implementations, example embodiments provide various aspects ofa graphical processing pipeline as discussed above to providepost-processing for layering (e.g., stacking) of respective mediaoverlays onto media content to render a composite media content, asdescribed further below.

FIG. 13 is a schematic diagram of an example of a graphical processingpipeline, namely a post-processing pipeline 1300 implemented forcomponents (e.g., a GPU) of the client device 102, according to someexample embodiments. More specifically, the example of FIG. 13illustrate a graphical processing pipeline where graphical operationsperformed on a given input frame are cumulative such that the inputframe is processed in accordance with a first selected media overlay andthe output of the processing is then provided as input for processing inaccordance with a second selected media overlay, and so on throughoutthe remaining stages of the graphical processing pipeline.

In an embodiment, the post-processing pipeline 1300 illustrated in FIG.13 (and also in FIG. 14 discussed below) implements an extensiblerendering engine which supports multiple image processing operationscorresponding to respective media overlays. Such an extensible renderingengine enables a reduction in the consumption memory resources of agiven electronic device (e.g., the client device 102) as a singlerendering engine can be loaded into memory for execution rather thanhaving multiple different rendering engines in memory, each occupyingdistinct memory spaces, as in some existing implementations.

In one example, the client device 102 is configured to implement one ormore of the stages of the post-processing pipeline 1300, which are shownas various media overlay layers 1310-1330 each corresponding to arespective media overlay. In an example, each media overlay layer1310-1330 is configurable, for instance, to perform one or more shaderand/or image processing operations corresponding to a particular mediaoverlay.

As shown in media overlay layer 1310, the post-processing pipeline 1300receives an original frame 1312 and performs post-processing operations1314 such as transformations, color effects, shader effects (e.g.,distortions), face effects, and the like, based on a first selectedmedia overlay, and outputs a processed frame 1316.

As shown in media overlay layer 1320, the post-processing pipeline 1300receives the processed frame 1316 and performs second post-processingoperations 1322 based on a second selected media overlay. A secondprocessed frame 1324 is provided as output to a subsequent media overlaylayer corresponding to media overlay layer 1330.

Further, as shown in media overlay layer 1330, the post-processingpipeline 1300 receives the second processed frame 1324 and performsthird post processing operations 1332 based on a third selected mediaoverlay. In another example, the media overlay layer 1330 is instead anoutput layer which generates pipeline output data (e.g., the secondprocessed frame 1324) for rendering whereby the third post processingoperations 1332 correspond to operations for the pipeline output data.

FIG. 14 is a schematic diagram of an example of a graphical processingpipeline, namely a post-processing pipeline 1400 implemented forcomponents (e.g., a GPU) of the client device 102, according to someexample embodiments. More specifically, the example of FIG. 14illustrate a graphical processing pipeline where graphical operationsare respectively performed on a given input frame such that the inputframe is processed in accordance to a first selected media overlay, andthe same (original) input frame is provided as input for processing inaccordance to a second selected media overlay, and the respectiveprocessed input frames and then composited together in a singlecomposite image for rendering. Thus, it is understood that FIG. 14differs from FIG. 13 in that each media overlay layer of thepost-processing pipeline in FIG. 14 are applied to the original inputframe.

As illustrated, the client device 102 is configured to implement one ormore of the stages of the post-processing pipeline 1400, which are shownas various media overlay layers 1410-1430 corresponding to respectivemedia overlays. In an example, each media overlay layer 1410-1430 isconfigurable, for instance, to perform one or more shader and/or imageprocessing operations corresponding to a particular media overlay.

As shown in media overlay layer 1410, the post-processing pipeline 1400receives an original frame 1412 and performs first post-processingoperations 1414 such as transformations, color effects, shader effects(e.g., distortions), face effects, and the like, and outputs processedframe 1416.

As shown in media overlay layer 1420, the post-processing pipeline 1400receives the original frame 1412 and performs second post-processingoperations 1422 based on a second selected media overlay, and outputsprocessed frame 1424. Prior to continuing to media overlay layer 1430,the post-processing pipeline 1400 generates a composite frame 1426 whichmerges blends or otherwise combines the processed frame 1416 and theprocessed frame 1424.

Further, as shown in media overlay layer 1430, the post-processingpipeline 1400 receives the composite frame 1426 and performs third postprocessing operations 1432 based on a third selected media overlay. Inanother example, the media overlay layer 1430 is instead an output layerwhich generates pipeline output data (e.g., the composite frame 1426)for rendering whereby the third post processing operations 1432correspond to operations for the pipeline output data.

FIG. 15 is a schematic diagram of an example of a stacking of mediaoverlay layers as implemented via a graphical processing pipeline,namely the post-processing pipeline(s) described above in FIG. 13 andFIG. 14, according to some example embodiments.

As illustrated in the example of FIG. 15, the stacking of media overlaylayers can be implemented and executed on computer processors 1510, suchas when provided by a given electronic device (e.g., the client device102). A first media overlay layer corresponding to a first media overlay1501 is applied to media content by the computer processors 1510. Asecond media overlay layer corresponding to a second media overlay 1502is applied to media content by the computer processors 1510. A thirdmedia overlay layer corresponding to a third media overlay 1503 isapplied to media content by the computer processors 1510. Further, afourth media overlay layer corresponding to a fourth media overlay 1504is applied to media content by the computer processors 1510. In thismanner, various media overlays can be stacked and applied to mediacontent for inclusion in a message.

Although four various layers are described as examples in FIG. 15, it isappreciated that fewer or more layers can be provided without departingfrom the scope of the subject technology.

As previously discussed, embodiments of subject technology enable thedelivery and organized presentation of media overlays forpost-processing media content, for use at a computing device (e.g., theclient device 102). In some examples, respective media overlays can bedisplayed in conjunction, during a post-processing stage, withpreviously captured media content (e.g., images and/or video). Asdescribed further herein, when a user performs a particular touch inputgesture (e.g., swipe, or drag gesture) within a user interface, aparticular a media overly is selected and presented to the user.

The particular media overlay may be selected according to a rankingwithin a set of media overlays and according to a ranking of the set ofmedia overlays. The particular media overlay can be selected accordingto a ranking among other media overlays within a specifiedclassification (e.g., filter type, LENSES type, and the like), accordingto a ranking across other media overlays of other classifications, or acombination thereof. In an embodiment, a set of media overlays can begrouped based on the same classification for presentation in a carouselinterface. Remaining media overlays in the set of media overlays mayalso be selected for presentation in the carousel interface as discussedbelow.

In some embodiments, a given electronic device (e.g., the client device102 and/or the messaging server system 108) determines a ranking scoreto each media overlay, from a normal distribution. In some embodiments,a respective media overlay (e.g., filter) can be given a “boost” inorder to boost distribution by N standard deviations. In an example,each media overlay may be assigned a default score (e.g., priority)based on a predetermined value (e.g., 500) within a predetermined rangeof values (e.g., 0 to 1000). The ranking score can be considered anindicator of relevancy for the respective media overlay in an example.Such an indicator of relevancy (e.g., relevance score or metric) can bebased on various signals including, for example, a geolocation, a timeor date, an object that is recognized in the retrieved image data,usage, and the like. Based on such signals the ranking score can beadjusted higher or lower to indicate whether the media overlay isconsidered more or less relevant, respectively, with respect to theretrieved image data and/or a classification (e.g., type) associatedwith the media overlay.

In some embodiments, presentation of media overlays within the userinterface can be determined utilizing machine learning techniques. Anelectronic device (e.g., the client device 102) may learn whether amedia overlay belongs to one classification or another. The electronicdevice may utilize a ranking approach to evaluate relevancy and priorityof a media overlay relating to the classification (e.g., name ordescription, numerical indicator, universally unique identifier (UUID),and the like) and the ordering of its corresponding record of mediaoverlays. The record of media overlays can be any appropriate datastructure, including for example, a table, a list, an array, a vector, afile, and the like. After adding a media overlay into the record, theelectronic device may alter or move the media overlay to change theorder in which the media overlay appears in a presentation of mediaoverlays within the user interface. In an example, the electronic devicemay remove less relevant or lower priority media overlays from storage,for example, increasing storage available for user-generated content.The electronic device or a server may prioritize delivery over a networkof more relevant or higher priority media overlays or sets of mediaoverlays, for example, improving responsiveness of the user interfacewhen selecting certain media overlays.

A set of media overlays can include any number of media overlays.However, it is appreciated, in some embodiments, the number of mediaoverlays provided for inclusion with the user interface is constrainedbased on a predetermined limit to facilitate a reduction in utilizationof computing resources (e.g., memory, display power, battery, etc.).Media overlays in a set may be ordered, ranked, prioritized, orotherwise organized according to one or more predetermined criteria suchas based on a media overlay type as discussed further below. Each set(e.g., group) of media overlays in a plurality of sets of media overlaysmay be ordered, ranked, prioritized, or otherwise organized according toone or more predetermined criteria (e.g., usage and the like). Each setof media overlays may include any number of distinct media overlaysorganized based on a media overlay type as discussed further below.Further, media overlays may be organized, prioritized, or otherwisearranged in each set according to usage, rank, and the like.

In some embodiments, an electronic device (e.g., the client device 102and/or one or more components of the messaging server system 108)selects the set of media overlays by comparing or matching aclassification (e.g., same media overlay type) associated with one ormore media overlays in the set of media overlays.

In some embodiments, each media overlay corresponding to a media overlayis associated with at least one classification (e.g., a categoryassociated with a given media overlay). Classifications may correspondvarious categories (e.g., a classification label or category indicatorfor the media overlay), which are then utilized for organizing (e.g.,grouping) respective media overlays into various sets (e.g., groups) forincluding with a user interface for presenting (and interaction) with agiven user of the electronic device. Based at least in part on suchgroupings, the user can select multiple media overlays, via the userinterface, for applying to media content during a post-processing stageas discussed with respect to FIG. 16 and FIG. 17. Variousclassifications of media overlays are discussed in more detail in theexamples of FIG. 18 to FIG. 25.

Further, in an implementation, whether a media overlay is selected forinclusion in the carousel is dependent on whether a media overlayapplicable context includes information indicating that the mediaoverlay is considered a post-capture media overlay (e.g., can bepreviewed or rendered for display by the electronic device on mediacontent during post-processing). The media overlay applicable contexttherefore may be used to determine that the media overlay can beapplied, with respect to media content, as a post-processing imageoperation in a post-capture stage. In another example, a context isdetermined based on a determination that the client device 102 and/orthe messaging client application 104 has accessed media content formodifying during a post-capture time period, which in turn initiates theprocess for populating the record of media overlays that is thenutilized for selecting media overlays for presenting in the carousel.

FIG. 16 illustrates examples of user interfaces comprising a carouselfor selecting and stacking multiple media overlays for applyingpost-processing to media content (e.g., an image or video) in themessaging client application 104 (or the messaging system 100),according to some embodiments.

In embodiments of such user interfaces, selectable graphical items 1650may be presented in a carousel arrangement in which a portion or subsetof the selectable graphical items 1650 are visible on a display screenof a given computing device (e.g., the client device 102). By way ofexample, the user can utilize various inputs to rotate the selectablegraphical items onto and off of the display screen in mannercorresponding to a carousel providing a cyclic view of the graphicalitems. The carousel arrangement as provided in the user interfacestherefore allow multiple graphical items to occupy a particulargraphical area on the display screen.

As described herein, media overlays can be organized into respectivegroups for including on the carousel arrangement thereby enablingrotating through media overlays by group. Further, media overlays can beselected for inclusion based on various signals including, for example,time, date, geolocation, metadata associated with the media content, andthe like. Similarly, media overlays can be grouped based on suchsignals. Moreover, a score can be generated and assigned to each mediaoverlay, and based at least in part on the respective scores, a subsetof the media overlays are selected for inclusion on the carouselarrangement of the user interface in an example. In the carouselarrangement of the user interface examples of FIG. 16, respective mediaoverlays are selected from different groups of media overlays asdiscussed below.

In the following discussion, the selectable graphical items correspondto respective media overlays that are applied to media content as partof post-processing. During post-processing the media content has beenpreviously captured and then retrieved from storage. As illustrated inuser interface 1600, selectable graphical items 1650, corresponding to acarousel arrangement, includes a selectable graphical item 1651 in thedisplay screen of an electronic device (e.g., the client device 102).The selectable graphical item 1650 is selected via a touch input by theuser.

In a second example of FIG. 16, the user instead provides a differenttouch input corresponding to a swipe or drag gesture that enablesscrolling through (e.g., providing navigation through various graphicalitems presented in the user interface 1600) the selectable graphicalitems 1650, and a second selectable graphical item 1652 is displayed inresponse to the swipe or drag gesture. The second selectable graphicalitem 1652, as indicated in the user interface 1600, belongs to the samegroup of media overlays as the selectable graphical item 1650.

In a third example of FIG. 16, the user continues the swipe or draggesture which results in a display of a third selectable graphical item1654 in the user interface 1600. In this example, the third selectablegraphical item 1654 also belongs to the same group of media overlays asthe respective media overlays corresponding to the selectable graphicalitem 1651 and the second selectable graphical item 1652. To apply themedia overlay corresponding to the third selectable graphical item 1654,a further input may be provided by the user such as another touch input(e.g., tap, or press).

In the third example, the user provides a subsequent input (e.g., a tapor press) in order to apply the media overlay corresponding to the thirdselectable graphical item 1654. In response, a media overlay 1656 isapplied and provided for display in the user interface 1600 on thedisplay screen. After applying the media overlay 1656, the userinterface 1600 provides an indication that the third selectablegraphical item 1654 was previously selected (e.g., by highlighting thethird selectable graphical item 1654).

In a fourth example of FIG. 16, the user then provides a subsequentswipe or drag gesture that further enables scrolling through theselectable graphical items 1650. In an embodiment, due to display arearestrictions of the carousel arrangement, the user interface displaysthe third selectable graphical item 1654 as a smaller version of itself,while also having other selectable graphical items be hidden (ordisappear) from the carousel arrangement. In response to the swipe ordrag gesture, the user interface 1600 displays a fourth selectablegraphical item 1658, which based on the graphical indication, belongs toa different group of media overlays than the first group including themedia overlay corresponding to the previously selected third selectablegraphical item 1654. The user can continue the swipe or drag gesture (oralternatively start a new swipe or drag gesture) to scroll through otherselectable graphical items for further selecting an additional mediaoverlay (e.g., in a different media overlay group).

FIG. 17 illustrates additional examples of user interfaces (e.g.,carousel) for selecting and stacking multiple media overlays forapplying post-processing to media content (e.g., an image or video) inthe messaging client application 104 (or the messaging system 100),according to some embodiments. FIG. 17 is discussed by reference to FIG.16 as the examples of FIG. 17 are provided in conjunction with theexamples of FIG. 16.

In the examples shown in FIG. 17, the user interface 1600 as describedabove in FIG. 16 is provided for display on the display screen of anelectronic device (e.g., the client device 102).

In a first example of FIG. 17, continuing from the fourth examplediscussed in FIG. 16, a selectable graphical item 1751 is included inselectable graphical items 1750, corresponding to a carouselarrangement, as displayed in the user interface 1600. As further shown,the third selectable graphical item 1654 and the fourth selectablegraphical item 1658 previously discussed in FIG. 16 are included in theselectable graphical items 1750 of FIG. 17. In this example, theselectable graphical item 1751, which based on the graphical indication,belongs to the same group of media overlays as the fourth selectablegraphical item 1658 (which was not selected as discussed above). Theuser provides a further gesture input (e.g., swipe or drag gesture) toscroll through other selectable graphical items 1750 corresponding todifferent media overlays.

In a second example of FIG. 17, the user continues the swipe or draggesture which results in a display of a selectable graphical item 1752in the user interface 1600. The selectable graphical item 1752, whichbased on the graphical indication, belongs to a different group of mediaoverlays than the group of media overlays corresponding to theselectable graphical item 1751 and the fourth selectable graphical item1658. In an embodiment, due to display area restrictions of the carouselarrangement, the user interface 1600 displays a selectable graphicalitem 1756 that represents the group of media overlays including theselectable graphical item 1751 and the fourth selectable graphical item1658. Further, in the carousel arrangement, the user interface 1600includes a selectable graphical item 1754 that represents the group ofmedia overlays including the selectable graphical item 1651, the secondselectable graphical item 1652, and the third selectable graphical item1654 (which was previous selected to apply the media overlay 1656).

In this second example, the user provides a subsequent input (e.g., atap or press) in order to apply the media overlay corresponding to theselectable graphical item 1752. To provide layering (e.g., stacking) ofdifferent media overlays, a media overlay 1758 is applied in response tothe subsequent input, where the media overlay 1758 is provided fordisplay in the user interface 1600 in conjunction with the displayedmedia overlay 1656. After applying the media overlay 1758, the userinterface 1600 provides an indication that the selectable graphical item1752 was previously selected (e.g., by highlighting the selectablegraphical item 1752).

The following discussion relates to examples of different types of mediaoverlays in accordance with some embodiments of the subject technology.In an example, a media overlay type indicates a particular categorywhich can be utilized for grouping an associated media overlay. Asdiscussed above, such a grouping of media overlays can then be presentedin a carousel arrangement interface where selectable graphical items areincluded for selecting one or more media overlays, which can be stackedor applied or layered in combination as part of post-processing mediacontent. The example media overlays illustrated in the discussion of thefollowing figures can be selected for inclusion in respective groups,based on the aforementioned ranking and/or selection techniques, withinthe carousel interface discussed above in FIG. 16 and FIG. 17.

FIG. 18 illustrates examples of media overlays that can be selected toapply on media content during post-processing. As illustrated, a set ofgeolocation-based media overlays are shown in the examples of FIG. 18including media overlay 1810, media overlay 1820, media overlay 1830,and media overlay 1840. Such geolocation media overlays, in at leastsome embodiments, includes static media overlays specific to ageolocation, or dynamic media overlays with location.

FIG. 19 illustrates examples of media overlays that can be selected toapply on media content during post-processing. As illustrated, a set ofday-based media overlays are shown in the examples of FIG. 19 includingmedia overlay 1910, media overlay 1920, media overlay 1930, and mediaoverlay 1940. Such day media overlays, in at least some embodiments,includes media overlays that indicate the day (e.g., a particular day ofthe week, or a holiday, and the like), or media overlays with relevanceto the particular current day.

FIG. 20 illustrates examples of media overlays that can be selected toapply on media content during post-processing. As illustrated, a set ofevent-based media overlays are shown in the examples of FIG. 20including media overlay 2010, media overlay 2020, media overlay 2030,and media overlay 2040. Such event media overlays, in at least someembodiments, includes media overlays for a specific event, mediaoverlays utilized for live story production, sports (e.g., sports teamsand the like) media overlays, and media overlays that are flighted(e.g., activated) to smaller areas and shorter time frames.

FIG. 21 illustrates examples of media overlays that can be selected toapply on media content during post-processing. As illustrated, a set ofmoment-based media overlays are shown in the examples of FIG. 21including media overlay 2110, media overlay 2120, media overlay 2130,and media overlay 2140. Such moment media overlays, in at least someembodiments, includes hyper contextual media overlays for a particularmessage, media overlays that are flighted (e.g., activated) for shortertime frames and/or specific purpose, media overlays that have advancedtargeting conditions including friend/social network media overlays(e.g., a friend is used as a context), time-based (morning/night),visual context based, deep link (e.g., specifying a location in an appdefined by the deep link), and the like.

FIG. 22 illustrates examples of media overlays that can be selected toapply on media content during post-processing. As illustrated, a set ofdecorative based media overlays are shown in the examples of FIG. 22including media overlay 2210, media overlay 2220, media overlay 2230,and media overlay 2240. Such decorative media overlays, in at least someembodiments, includes non-message based media overlays where a primarypurpose is decoration, absent of words or expression, and can beflighted at any time, and/or anywhere, and also flighted seasonal insome instance.

FIG. 23 illustrates examples of media overlays that can be selected toapply on media content during post-processing. As illustrated, a set ofvibe-based media overlays are shown in the examples of FIG. 23 includingmedia overlay 2310, media overlay 2320, media overlay 2330, and mediaoverlay 2340. Such vibe media overlays, in at least some embodiments,includes media overlays that are have general, non-contextualexpressions, contains expressive copy, often targeted towardsemotions/vibes, and can be flighted at any time in a particular localeor geolocation.

FIG. 24 illustrates examples of media overlays that can be selected toapply on media content during post-processing. As illustrated, a set ofpersonal based media overlays are shown in the examples of FIG. 24including media overlay 2410, media overlay 2420, media overlay 2430,and media overlay 2440. Such personal media overlays, in at least someembodiments, includes media overlays that are personalized to the user,can include a BITMOJI (e.g., respective user icon or user avatar),user's name, or is suitable for selfies (e.g., self-portraits using afront facing).

FIG. 25 illustrates examples of media overlays that can be selected toapply on media content during post-processing. As illustrated, a set ofinfo template-based media overlays are shown in the examples of FIG. 25including media overlay 2510, media overlay 2520, media overlay 2530,and media overlay 2540. Such info template media overlays, in at leastsome embodiments, includes media overlays with a combination of dynamictext as main content of media overlay, having minimal or no directmessage aside from dynamic text, and can have a decorative, minimal, orno template background.

FIG. 26 is a flowchart illustrating a method 2600 to generate a messagebased on at least one post-processing operation on image data, accordingto certain example embodiments. The method 2600 may be embodied incomputer-readable instructions for execution by one or more computerprocessors such that the operations of the method 2600 may be performedin part or in whole by the messaging client application 104,particularly with respect to respective components of the annotationsystem 206 described above in FIG. 6; accordingly, the method 2600 isdescribed below by way of example with reference thereto. However, itshall be appreciated that at least some of the operations of the method2600 may be deployed on various other hardware configurations and themethod 2600 is not intended to be limited to the messaging clientapplication 104.

At operation 2602, the post-processing engine 620 retrieves first imagedata from a storage device. The first image data may be an image such asa photograph or frame of a video captured by the electronic device at aprevious time. For example, as described above with respect to at leastFIG. 6, the first image data is captured by the client device 102 at aprevious time, stored to the storage device, and later retrieved by thepost-processing engine 620.

At operation 2604, the post-processing engine 620 receives firstmetadata corresponding to a selected image processing operation (e.g.,media overlay). Such metadata may be stored with and/or generated by theclient device 102 (or stored in the database 102) in order to enablepost-processing of media content (e.g., as described in FIG. 6 and FIG.7). For example, as described before in respect to at least FIG. 6 andFIG. 7, metadata or information corresponding to a media overlay to beapplied to media content (e.g., the first image data) is provided (e.g.,either by the client 102 and/or the messaging server system 108) duringpost-processing to enable performing the selected image processingoperation. Moreover, the selected image processing operation is selectedvia a display of the client device (e.g., using a swipe gesture asdescribed, for example, in at least FIG. 11, FIG. 12, FIG. 16, and FIG.17). In an embodiment, the selected image processing operationcorresponds to a media overlay that belongs to a particular group ofmedia overlays based on a category associated with the media overlay.

At operation 2606, the post-processing engine 620 generates second imagedata based at least in part on the first metadata and the imageprocessing operation performed on the received first image data. Forexample, as described before in at least FIG. 9A, FIG. 9B, FIG. 10A,FIG. 10B, FIG. 16, and FIG. 17, the client device 102 applies an imageprocessing operation corresponding to a selected media overlay to mediacontent (e.g., to enable a rendering of the applied media overlay on thedisplay screen of the client device 102). The rendering engine 630renders, for display by the client device, the second image datacomprising a first image corresponding to the first image data modifiedby the selected image processing operation, as described before in atleast FIG. 6.

In a further example, the post-processing engine 620 receives sensordata including an orientation of the client device 102 corresponding tothe first image data, the sensor data including metadata associated withthe first image data, where generating second image data is furtherbased on the sensor data, the received sensor data indicating anorientation of the client device 102. For example, using a particulartracking engine (e.g., provided by the tracking engine 610) with thesensor data, the post-processing engine 620 detects the deviceorientation from the sensor data and then generates the second imagedata in a format to fit the device orientation and/or to appropriatelyprovide augmentation of the first image data to thereby generate thesecond image data. The post-processing engine 620 can store the secondimage data separately from the first image data in an embodiment.

In another example, the first image data includes a representation of anenvironment. The post-processing engine 620 performs a tracking processbased on the first image data. The tracking process can be tracking asurface recognized in the representation of the environment, tracking aface recognized in the representation of the environment, tracking anobject using a machine learning model, and so forth. In one exampleembodiment, only one tracking process is performed at a time by thepost-processing engine 620.

At operation 2608, the post-processing engine 620 generates secondmetadata comprising information related to the image processingoperation (e.g., media overlay). For example, the second metadatacomprises a first identifier associated with the first image data, andsecond identifier associated with the second image data, and/or othermetadata which is described before with respect to at least FIG. 7.Further, the second metadata, in some embodiments, can include thefollowing information to indicate that the image processing occurredduring a post-processing stage: gesture information (e.g., swipedirection), gesture sequence count (e.g., number in a sequence or seriesof swipes), tap count (e.g., number of tap/touch inputs received), mediaoverlay name, media overlay type (e.g., classification indicator), mediaoverlay index, number of media overlays, media overlay score (e.g.,relevance indicator), media overlay group, and the like.

At operation 2610, the sharing engine 640 generates a message comprisingthe second metadata, the second image data, and the first image data.For example, such a message can include each of the aforementionedinformation, which described before in respect to at least FIG. 7.

At operation 2612, the sharing engine 640 sends, to a server (e.g., themessaging server system 108), the message for sharing with one or moreother client devices. For example, the sharing engine 640 sends such amessage as described before in respect to at least FIG. 6.

FIG. 27 is a flowchart illustrating a method 2700 to generate a messagebased on layering of post-processing operations on image data, accordingto certain example embodiments. The method 2700 may be embodied incomputer-readable instructions for execution by one or more computerprocessors such that the operations of the method 2700 may be performedin part or in whole by the messaging client application 104,particularly with respect to respective components of the annotationsystem 206 described above in FIG. 6; accordingly, the method 2700 isdescribed below by way of example with reference thereto. However, itshall be appreciated that at least some of the operations of the method2700 may be deployed on various other hardware configurations and themethod 2700 is not intended to be limited to the messaging clientapplication 104.

At operation 2702, the post-processing engine 620 retrieves first imagedata from a storage device. As described above, the first image data iscaptured by the client device 102 at a previous time stored to thestorage device, and later retrieved by the post-processing engine 620 inan example described in respect to at least FIG. 6.

At operation 2704, the post-processing engine 620 detects a selection ofa first media overlay corresponding to a first image processingoperation. For example, as described before in at least FIG. 11, FIG.12, FIG. 16, and FIG. 17, a media overlay is selected by a user via aninput (e.g., touch input, swipe gesture, and the like). Further, theselected first media overlay is associated with a particular group ofmedia overlays based on a category associated with each of the mediaoverlays.

At operation 2706, the post-processing engine 620 performs the firstimage processing operation corresponding to the first media overlay onthe first image data to generate second image data. For example, asdescribed before in at least FIG. 9A, FIG. 9B, FIG. 10A, and FIG. 10B, aselected media overlay is applied to media content (e.g., to enable arendering of the applied media overlay on the display screen of theclient device 102). Further, the first image processing operation isperformed by a first layer of a graphical processing pipeline asdescribed before in at least FIG. 13, FIG. 14, and FIG. 15.

At operation 2708, the post-processing engine 620 detects a selection ofa second media overlay corresponding to a second image processingoperation. For example, as described before in at least FIG. 16, andFIG. 17, a second media overlay can be selected by a user via an input(e.g., touch input, swipe gesture, and the like). Further, the secondmedia overlay corresponding to the second image processing operation isassociated with a second group of second media overlays based on adifferent category associated with the second media overlay.

At operation 2710, the post-processing engine 620 performs the secondimage processing operation on the second image data to generate thirdimage data. For example, as described before in at least FIG. 16, andFIG. 17, a second media overlay can be applied to media content that hasbeen processed before (e.g., with the first media overlay) to providelayering of media overlays to the media content. Further, the secondimage processing operation is performed by a second layer of thegraphical processing pipeline as described before in at least FIG. 13,FIG. 14, and FIG. 15. The second layer is executed after the first layerin an embodiment.

At operation 2712, the sharing engine 640 generates a message comprisingthe third image data As described before in at least FIG. 6, FIG. 7,FIG. 13, FIG. 14, FIG. 15, FIG. 16, and FIG. 17, multiple media overlayscan be applied on media content to provide a composite image, which atleast includes a combination of the applied media content. The sharingengine 640 can send the generated message to a server (e.g., themessaging server system 108) for sharing with one or more other clientdevices.

FIG. 28 is a flowchart illustrating a method 2800 to provide a carouselinterface for post-processing operations, according to certain exampleembodiments. The method 2800 may be embodied in computer-readableinstructions for execution by one or more computer processors such thatthe operations of the method 2800 may be performed in part or in wholeby the messaging client application 104, particularly with respect torespective components of the annotation system 206 described above inFIG. 6; accordingly, the method 2800 is described below by way ofexample with reference thereto. However, it shall be appreciated that atleast some of the operations of the method 2800 may be deployed onvarious other hardware configurations and the method 2800 is notintended to be limited to the messaging client application 104.

At operation 2802, the post-processing engine 620 retrieves, by a clientdevice from a storage device, first image data previously captured bythe client device (e.g., the client device 102). As described above, thefirst image data is captured by the client device 102 at a previoustime, stored to the storage device, and later retrieved by thepost-processing engine 620 in an example described in at least FIG. 6.The first image data is then displayed on the display screen of theclient device 102 in some embodiments.

At operation 2804, the post-processing engine 620 selects a set of mediaoverlays in response to displaying the first image data. In an example,each respective media overlay is associated with a category indicator.The client device 102 matches the category indicator among respectivemedia overlays to determine one or more groupings of media overlaysbased on the respective category indicators. The client device 102selects one of the groupings for the selected set of media overlays, asdescribed before in at least FIG. 16 and FIG. 17. In another example,the client device 102 selects multiple groups of media overlays.

In an embodiment, each respective media overlay is associated with ascore which may correspond to an indicator of relevancy for eachrespective media overlay (e.g., higher score indicating higherrelevancy, and lower score indicator lower relevancy). As discussedbefore, the indicator of relevancy can be based on an initial defaultscore or value, and then adjusted higher or lower based on one or moresignals (e.g., geolocation, time or date, usage, object of interest inthe image data, and the like). The post-processing engine 620 ranks themedia overlays based on the respective score associated with each mediaoverlay. In this example, the post-processing engine 620 selects apredefined number of highest ranked media overlays as the set of mediaoverlays. In another embodiment, the ranking is instead performed bycomponents of the messaging server system 108 and a set of selectedmedia overlays based on the determined ranking can be subsequentlyprovided to the post-processing engine 620 for processing in the mannerdescribed above. In an example where a single grouping of media overlayshas been selected (e.g., based on a sole matching category indicator),the ranking can be performed on the respective scores of each mediaoverlay within this same single grouping. In an example where multiplegroupings of media overlays have been selected (e.g., based on differentcategory indicators), the ranking can be performed on the respectivescores of each media overlay within each respective grouping of mediaoverlays.

At operation 2806, the post-processing engine 620 causes display of acarousel interface including selectable graphical items (e.g., the userinterface 1600). Each selectable graphical item of the selectablegraphical items corresponds to a respective media overlay of the set ofmedia overlays. In an embodiment, the selectable graphical items areprovided in the carousel interface based at least in part on theaforementioned ranking of media overlays where the top ranked mediaoverlays are selected for display. Thus, it is appreciated that eachselectable graphical item in the carousel interface can correspond toone of the top ranked media overlays. Moreover, as described in respectto at least FIG. 16, and FIG. 17, the carousel interface is presented onthe display screen of the client device 102. As described before,multiple groupings of media overlays can be provided for display in thecarousel interface, and respective media overlays from particulargroupings (e.g., based on matching category indicators) are provided fordisplay based on the aforementioned ranking (e.g., where top rankedmedia overlays are provided for display). In an example, the userinterface 1600 provides a visual indicator that distinguishes theselected first selectable graphical item from other selectable graphicalitems of the plurality of selectable graphical items that have not beenselected. Additionally, the selected first selectable graphical item iswithin a first display area and the first display area is different froma second display area where the other selectable graphical items of theplurality of selectable graphical items that have not been selected arepresented.

At operation 2808, the post-processing engine 620 receives a selectionof a first selectable graphical item from the plurality of selectablegraphical items. For example, as described before in at least FIG. 16,and FIG. 17, a particular media overlay corresponding to a particularselectable graphical item can be selected by a user via an input (e.g.,touch input, and the like).

At operation 2810, the post-processing engine 620 applies, to the firstimage data, a first media overlay corresponding to the selected firstselectable graphical item. For example, as described before in at leastFIG. 16, and FIG. 17, a selected media overlay can be applied to mediacontent (e.g., to enable a rendering of the applied media overlay on thedisplay screen of the client device 102).

FIG. 29 is a flowchart illustrating a method 2900 to determine a set ofmedia overlays for populating a set of media overlays that can beutilized by a client electronic device during a post-processing stage tomodify media content, according to certain example embodiments. Themethod 2900 may be embodied in computer-readable instructions forexecution by one or more computer processors such that the operations ofthe method 2900 may be performed in part or in whole by the messagingserver system 108; accordingly, the method 2900 is described below byway of example with reference thereto. However, it shall be appreciatedthat at least some of the operations of the method 2900 may be deployedon various other hardware configurations and the method 2900 is notintended to be limited to the messaging server system 108.

At operation 2902, the messaging server system 108 receives metadatacorresponding to a media overlay. In an example, the metadata can bestored in database 120 accessible via the database server 118.Alternatively, the metadata is stored by the client 102 (e.g., as partof storage associated with the messaging client application 104). Themetadata comprises information indicating that the media overlay isconfigured to be applied as an image processing operation duringpost-processing of image data during a post-capture stage. For example,as described before in at least FIG. 6, and FIG. 7, such metadatarelated to a media overlay may be utilized for enabling post-processingoperations by the messaging server system 108.

At operation 2904, the messaging server system 108 selects the mediaoverlay indicated in the metadata corresponding to the media overlay.For example, as described before in respect to at least FIG. 16, andFIG. 17, the messaging server system 108 determines that a media overlayis selected by determining whether a media overlay applicable contextincludes information indicating that the media overlay is considered apost-capture media overlay (e.g., can be previewed or rendered fordisplay by the electronic device on media content duringpost-processing). In one example, the media overlay applicable contextis determined by the messaging server system 108 by detecting that theclient device 102 and/or the messaging client application 104 hasaccessed media content for modification during a post-capture timeperiod, which in turn initiates an operation for populating the recordof media overlays that is then utilized for selecting media overlays forpresenting in a user interface (e.g., the user interface 1600).

At operation 2906, the messaging server system 108, based at least inpart on a category indicator associated with the respective mediaoverlay, populates a group of media overlays with at least therespective media overlay. For example, as described before in respect toat least FIG. 16 and FIG. 17, the messaging server system 108 determinesa number of media overlays for including in the group of media overlaysby determining that the group of media overlays includes a set of mediaoverlays that is less than a particular number of media overlayscorresponding to a maximum limit (or cap) of media overlays to include.Additionally, the messaging server system 108 determines a number ofmedia overlays for including in the group of media overlays, anddeclines to include a particular media overlay based at least in part ondetermining that the group of media overlays includes a set of mediaoverlays that meets the number of media overlays.

At operation 2908, the messaging server system 108 sends, to a clientdevice, second metadata comprising information related to the group ofmedia overlays. For example, the second metadata comprises informationindicating that each media overlay in the group of media overlayscorresponds to a same media overlay type. Alternatively, the informationindicates that only a subset of media overlays from the group of mediaoverlays corresponds to a same media overlay type. Also, in an example,the messaging server system 108 sends the second metadata comprisinginformation related to the group of media overlays is in response to theclient electronic device accessing a particular selectable graphicalitem in a carousel interface (e.g., the user interface 1600).

FIG. 30 is a block diagram illustrating an example software architecture3006, which may be used in conjunction with various hardwarearchitectures herein described. FIG. 30 is a non-limiting example of asoftware architecture and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 3006 may execute on hardwaresuch as machine 3100 of FIG. 31 that includes, among other things,processors 3104, memory 3114, and (input/output) I/O components 3118. Arepresentative hardware layer 3052 is illustrated and can represent, forexample, the machine 3100 of FIG. 31. The representative hardware layer3052 includes a processing unit 3054 having associated executableinstructions 3004. Executable instructions 3004 represent the executableinstructions of the software architecture 3006, including implementationof the methods, components, and so forth described herein. The hardwarelayer 3052 also includes memory and/or storage modules memory/storage3056, which also have executable instructions 3004. The hardware layer3052 may also comprise other hardware 3058.

In the example architecture of FIG. 30, the software architecture 3006may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 3006may include layers such as an operating system 3002, libraries 3020,frameworks/middleware 3018, applications 3016, and a presentation layer3014. Operationally, the applications 3016 and/or other componentswithin the layers may invoke API calls 3008 through the software stackand receive a response as in response to the API calls 3008. The layersillustrated are representative in nature and not all softwarearchitectures have all layers. For example, some mobile or specialpurpose operating systems may not provide a frameworks/middleware 3018,while others may provide such a layer. Other software architectures mayinclude additional or different layers.

The operating system 3002 may manage hardware resources and providecommon services. The operating system 3002 may include, for example, akernel 3022, services 3024, and drivers 3026. The kernel 3022 may act asan abstraction layer between the hardware and the other software layers.For example, the kernel 3022 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 3024 may provideother common services for the other software layers. The drivers 3026are responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 3026 include display drivers, cameradrivers, Bluetooth® drivers, flash memory drivers, serial communicationdrivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers,audio drivers, power management drivers, and so forth depending on thehardware configuration.

The libraries 3020 provide a common infrastructure that is used by theapplications 3016 and/or other components and/or layers. The libraries3020 provide functionality that allows other software components toperform tasks in an easier fashion than to interface directly with theunderlying operating system 3002 functionality (e.g., kernel 3022,services 3024 and/or drivers 3026). The libraries 3020 may includesystem libraries 3044 (e.g., C standard library) that may providefunctions such as memory allocation functions, string manipulationfunctions, mathematical functions, and the like. In addition, thelibraries 3020 may include API libraries 3046 such as media libraries(e.g., libraries to support presentation and manipulation of variousmedia format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphicslibraries (e.g., an OpenGL framework that may be used to render 2D and3D in a graphic content on a display), database libraries (e.g., SQLitethat may provide various relational database functions), web libraries(e.g., WebKit that may provide web browsing functionality), and thelike. The libraries 3020 may also include a wide variety of otherlibraries 3048 to provide many other APIs to the applications 3016 andother software components/modules.

The frameworks/middleware 3018 (also sometimes referred to asmiddleware) provide a higher-level common infrastructure that may beused by the applications 3016 and/or other software components/modules.For example, the frameworks/middleware 3018 may provide various graphicuser interface (GUI) functions, high-level resource management,high-level location services, and so forth. The frameworks/middleware3018 may provide a broad spectrum of other APIs that may be used by theapplications 3016 and/or other software components/modules, some ofwhich may be specific to a particular operating system 3002 or platform.

The applications 3016 include built-in applications 3038 and/orthird-party applications 3040. Examples of representative built-inapplications 3038 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. Third-party applications 3040 may include anapplication developed using the ANDROID™ or IOS™ software developmentkit (SDK) by an entity other than the vendor of the particular platform,and may be mobile software running on a mobile operating system such asIOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. Thethird-party applications 3040 may invoke the API calls 3008 provided bythe mobile operating system (such as operating system 3002) tofacilitate functionality described herein.

The applications 3016 may use built in operating system functions (e.g.,kernel 3022, services 3024 and/or drivers 3026), libraries 3020, andframeworks/middleware 3018 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systemsinteractions with a user may occur through a presentation layer, such aspresentation layer 3014. In these systems, the application/component“logic” can be separated from the aspects of the application/componentthat interact with a user.

FIG. 31 is a block diagram illustrating components of a machine 3100,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 31 shows a diagrammatic representation of the machine3100 in the example form of a computer system, within which instructions3110 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 3100 to perform any oneor more of the methodologies discussed herein may be executed. As such,the instructions 3110 may be used to implement modules or componentsdescribed herein. The instructions 3110 transform the general,non-programmed machine 3100 into a particular machine 3100 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 3100 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 3100 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 3100 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smart phone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 3110, sequentially or otherwise, that specify actions to betaken by machine 3100. Further, while only a single machine 3100 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 3110 to perform any one or more of the methodologiesdiscussed herein.

The machine 3100 may include processors 3104, memory/storage 3106, andI/O components 3118, which may be configured to communicate with eachother such as via a bus 3102. The memory/storage 3106 may include amemory 3114, such as a main memory, or other memory storage, and astorage unit 3116, both accessible to the processors 3104 such as viathe bus 3102. The storage unit 3116 and memory 3114 store theinstructions 3110 embodying any one or more of the methodologies orfunctions described herein. The instructions 3110 may also reside,completely or partially, within the memory 3114, within the storage unit3116, within at least one of the processors 3104 (e.g., within theprocessor's cache memory), or any suitable combination thereof, duringexecution thereof by the machine 3100. Accordingly, the memory 3114, thestorage unit 3116, and the memory of processors 3104 are examples ofmachine-readable media.

The I/O components 3118 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 3118 that are included in a particular machine 3100 willdepend on the type of machine. For example, portable machines such asmobile phones will likely include a touch input device or other suchinput mechanisms, while a headless server machine will likely notinclude such a touch input device. It will be appreciated that the I/Ocomponents 3118 may include many other components that are not shown inFIG. 31. The I/O components 3118 are grouped according to functionalitymerely for simplifying the following discussion and the grouping is inno way limiting. In various example embodiments, the I/O components 3118may include output components 3126 and input components 3128. The outputcomponents 3126 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 3128 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 3118 may includebiometric components 3130, motion components 3134, environmentalcomponents 3136, or position components 3138 among a wide array of othercomponents. For example, the biometric components 3130 may includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 3134 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 3136 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 3138 mayinclude location sensor components (e.g., a GPS receiver component),altitude sensor components (e.g., altimeters or barometers that detectair pressure from which altitude may be derived), orientation sensorcomponents (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 3118 may include communication components 3140operable to couple the machine 3100 to a network 3132 or devices 3120via coupling 3124 and coupling 3122, respectively. For example, thecommunication components 3140 may include a network interface componentor other suitable device to interface with the network 3132. In furtherexamples, communication components 3140 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 3120 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 3140 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 3140 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components3140, such as, location via Internet Protocol (IP) geo-location,location via Wi-Fi® signal triangulation, location via detecting a NFCbeacon signal that may indicate a particular location, and so forth.

The following discussion relates to various terms or phrases that arementioned throughout the subject disclosure.

“Signal Medium” refers to any intangible medium that is capable ofstoring, encoding, or carrying the instructions for execution by amachine and includes digital or analog communications signals or otherintangible media to facilitate communication of software or data. Theterm “signal medium” shall be taken to include any form of a modulateddata signal, carrier wave, and so forth. The term “modulated datasignal” means a signal that has one or more of its characteristics setor changed in such a matter as to encode information in the signal. Theterms “transmission medium” and “signal medium” mean the same thing andmay be used interchangeably in this disclosure.

“Communication Network” refers to one or more portions of a network thatmay be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®network, another type of network, or a combination of two or more suchnetworks. For example, a network or a portion of a network may include awireless or cellular network and the coupling may be a Code DivisionMultiple Access (CDMA) connection, a Global System for Mobilecommunications (GSM) connection, or other types of cellular or wirelesscoupling. In this example, the coupling may implement any of a varietyof types of data transfer technology, such as Single Carrier RadioTransmission Technology (1×RTT), Evolution-Data Optimized (EVDO)technology, General Packet Radio Service (GPRS) technology, EnhancedData rates for GSM Evolution (EDGE) technology, third GenerationPartnership Project (3GPP) including 3G, fourth generation wireless (4G)networks, Universal Mobile Telecommunications System (UMTS), High SpeedPacket Access (HSPA), Worldwide Interoperability for Microwave Access(WiMAX), Long Term Evolution (LTE) standard, others defined by variousstandard-setting organizations, other long-range protocols, or otherdata transfer technology.

“Processor” refers to any circuit or virtual circuit (a physical circuitemulated by logic executing on an actual processor) that manipulatesdata values according to control signals (e.g., “commands”, “op codes”,“machine code”, etc.) and which produces corresponding output signalsthat are applied to operate a machine. A processor may, for example, bea Central Processing Unit (CPU), a Reduced Instruction Set Computing(RISC) processor, a Complex Instruction Set Computing (CISC) processor,a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), anApplication Specific Integrated Circuit (ASIC), a Radio-FrequencyIntegrated Circuit (RFIC) or any combination thereof. A processor mayfurther be a multi-core processor having two or more independentprocessors (sometimes referred to as “cores”) that may executeinstructions contemporaneously.

“Machine-Storage Medium” refers to a single or multiple storage devicesand/or media (e.g., a centralized or distributed database, and/orassociated caches and servers) that store executable instructions,routines and/or data. The term shall accordingly be taken to include,but not be limited to, solid-state memories, and optical and magneticmedia, including memory internal or external to processors. Specificexamples of machine-storage media, computer-storage media and/ordevice-storage media include non-volatile memory, including by way ofexample semiconductor memory devices, e.g., erasable programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), FPGA, and flash memory devices; magnetic disks such asinternal hard disks and removable disks; magneto-optical disks; andCD-ROM and DVD-ROM disks The terms “machine-storage medium,”“device-storage medium,” “computer-storage medium” mean the same thingand may be used interchangeably in this disclosure. The terms“machine-storage media,” “computer-storage media,” and “device-storagemedia” specifically exclude carrier waves, modulated data signals, andother such media, at least some of which are covered under the term“signal medium.”

“Component” refers to a device, physical entity, or logic havingboundaries defined by function or subroutine calls, branch points, APIs,or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components. A “hardware component”is a tangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a field-programmable gate array (FPGA) or an applicationspecific integrated circuit (ASIC). A hardware component may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software), may be driven by cost and timeconsiderations. Accordingly, the phrase “hardware component” (or“hardware-implemented component”) should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which hardwarecomponents are temporarily configured (e.g., programmed), each of thehardware components need not be configured or instantiated at any oneinstance in time. For example, where a hardware component comprises ageneral-purpose processor configured by software to become aspecial-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware components) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware component at one instanceof time and to constitute a different hardware component at a differentinstance of time. Hardware components can provide information to, andreceive information from, other hardware components. Accordingly, thedescribed hardware components may be regarded as being communicativelycoupled. Where multiple hardware components exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) between or among two or more of thehardware components. In embodiments in which multiple hardwarecomponents are configured or instantiated at different times,communications between such hardware components may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware components have access. Forexample, one hardware component may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware component may then, at alater time, access the memory device to retrieve and process the storedoutput. Hardware components may also initiate communications with inputor output devices, and can operate on a resource (e.g., a collection ofinformation). The various operations of example methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors 1004 orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an API). The performance ofcertain of the operations may be distributed among the processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processors orprocessor-implemented components may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented components may be distributed across a number ofgeographic locations.

“Carrier Signal” refers to any intangible medium that is capable ofstoring, encoding, or carrying instructions for execution by themachine, and includes digital or analog communications signals or otherintangible media to facilitate communication of such instructions.Instructions may be transmitted or received over a network using atransmission medium via a network interface device.

“Computer-Readable Medium” refers to both machine-storage media andtransmission media. Thus, the terms include both storage devices/mediaand carrier waves/modulated data signals. The terms “machine-readablemedium,” “computer-readable medium” and “device-readable medium” meanthe same thing and may be used interchangeably in this disclosure.

“Client Device” refers to any machine that interfaces to acommunications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops,multi-processor systems, microprocessor-based or programmable consumerelectronics, game consoles, set-top boxes, or any other communicationdevice that a user may use to access a network. In the subjectdisclosure, a client device is also referred to as an “electronicdevice.” “Ephemeral Message” refers to a message that is accessible fora time-limited duration. An ephemeral message may be a text, an image, avideo and the like. The access time for the ephemeral message may be setby the message sender. Alternatively, the access time may be a defaultsetting or a setting specified by the recipient. Regardless of thesetting technique, the message is transitory.

What is claimed is:
 1. A method, comprising: accessing, by one or morehardware processors, first image data; identifying, by the one or morehardware processors, based on the first image data, a target facialfeature; detecting, by the one or more hardware processors, a userselection of an image processing operation to modify the target facialfeature with a media overlay; performing, by the one or more hardwareprocessors, the image processing operation on the first image data usingthe media overlay to generate second image data, the second image dataincluding a modified target facial feature; and causing, by the one ormore hardware processors, display of the second image data on a userinterface of a device.
 2. The method of claim 1, wherein the imageprocessing operation on the first image data using the media overlay isperformed using a machine learning model.
 3. The method of claim 1,further comprising: using a machine learning model to generate areference facial feature base on training data.
 4. The method of claim3, wherein identifying the target facial feature comprises: identifying,based on the training data, a facial landmark of a face included in animage represented by the first image data; and determining, based on thefacial landmark, that the reference facial feature aligns with thetarget facial feature.
 5. The method of claim 1, further comprising:determining that the first image data represents a first face and asecond face, the first face including the target facial feature;detecting a first user selection of the first face to apply the imageprocessing operation; and based on the first user selection of the firstface and the user selection of the image processing operation,performing the image processing operation on the first image data usingthe media overlay to generate the second image data.
 6. The method ofclaim 5, further comprising: detecting a second user selection of thesecond face to apply a second image processing operation thatcorresponds to a second media overlay; and performing the second imageprocessing operation on the second image data using the second mediaoverlay to generate third image data.
 7. The method of claim 6, furthercomprising: causing display of the third image data on the userinterface of the device.
 8. The method of claim 1, wherein the firstimage data corresponds to an image that is captured via a camera coupledto the device.
 9. The method of claim 1, further comprising: generatinga message comprising the second image data; and sending, to a server,the message for sharing with one or more other devices.
 10. A systemcomprising: a processor; a memory including instructions that, whenexecuted by the processor, cause the processor to perform operationscomprising: accessing first image data; identifying, based on the firstimage data, a target facial feature; detecting a user selection of animage processing operation to modify the target facial feature with amedia overlay; performing the image processing operation on the firstimage data using the media overlay to generate second image data, thesecond image data including a modified target facial feature; andcausing display of the second image data on a user interface of adevice.
 11. The system of claim 10, wherein the image processingoperation on the first image data using the media overlay is performedusing a machine learning model.
 12. The system of claim 10, wherein theoperations further comprise: using a machine learning model to generatea reference facial feature base on training data.
 13. The system ofclaim 12, wherein the operations of identifying the target facialfeature further comprise: identifying, based on the training data, afacial landmark of a face included in an image represented by the firstimage data; and determining, based on the facial landmark, that thereference facial feature aligns with the target facial feature.
 14. Thesystem of claim 10, wherein the operations further comprise: determiningthat the first image data represents a first face and a second face, thefirst face including the target facial feature; detecting a first userselection of the first face to apply the image processing operation; andbased on the first user selection of the first face and the userselection of the image processing operation, performing the imageprocessing operation on the first image data using the media overlay togenerate the second image data.
 15. The system of claim 14, wherein theoperations further comprise: detecting a second user selection of thesecond face to apply a second image processing operation thatcorresponds to a second media overlay; and performing the second imageprocessing operation on the second image data using the second mediaoverlay to generate third image data.
 16. The system of claim 15,wherein the operations further comprise: causing display of the thirdimage data on the user interface of the device.
 17. The system of claim10, wherein the first image data corresponds to an image that iscaptured via a camera coupled to the device.
 18. The system of claim 10,wherein the operations further comprise: generating a message comprisingthe second image data; and sending, to a server, the message for sharingwith one or more other devices.
 19. A non-transitory computer-readablemedium comprising instructions, which when executed by a computingdevice, cause the computing device to perform operations comprising:accessing first image data; identifying, based on the first image data,a target facial feature; detecting a user selection of an imageprocessing operation to modify the target facial feature with a mediaoverlay; performing the image processing operation on the first imagedata using the media overlay to generate second image data, the secondimage data including a modified target facial feature; and causingdisplay of the second image data on a user interface of a device. 20.The non-transitory computer-readable medium of claim 19, wherein theimage processing operation on the first image data using the mediaoverlay is performed using a machine learning model.